chore(Logging): add DefaultAntiforgery filter rule

[ArgoZhang]

Link issues

fixes #8016

Summary By Copilot

Regression?

• Yes
• No

Risk

• High
• Medium
• Low

Verification

• Manual (required)
• Automated

Packaging changes reviewed?

• Yes
• No
• N/A

☑️ Self Check before Merge

⚠️ Please check all items below before review. ⚠️

• Doc is updated/provided or not needed
• Demo is updated/provided or not needed
• Merge the latest code from the main branch

Summary by Sourcery

Enhancements:

• Configure a specific log level override to suppress logs from Microsoft.AspNetCore.Antiforgery.DefaultAntiforgery in the file logger.

[sourcery-ai]

Reviewer's guide (collapsed on small PRs)

Reviewer's Guide

Configures logging to suppress messages from the ASP.NET Core DefaultAntiforgery component in the server project's logging configuration.

File-Level Changes

Change	Details	Files
Adjust logging configuration to disable DefaultAntiforgery logs for the server application.	Extend the LgbFile logger LogLevel section in appsettings.json to add an explicit log level override for Microsoft.AspNetCore.Antiforgery.DefaultAntiforgery, setting it to None Leave the server project file (BootstrapBlazor.Server.csproj) unchanged aside from any non-functional diff artifacts	src/BootstrapBlazor.Server/appsettings.json src/BootstrapBlazor.Server/BootstrapBlazor.Server.csproj

Assessment against linked issues

Issue	Objective	Addressed	Explanation
#8016	Add a logging filter rule for Microsoft.AspNetCore.Antiforgery.DefaultAntiforgery to the application logging configuration.	✅

Possibly linked issues

• chore(Logging): add DefaultAntiforgery filter rule #8016: PR updates appsettings.json logging configuration to add the DefaultAntiforgery filter rule requested in the issue.
• chore(Logging): add DefaultAntiforgery filter rule #8016: The PR implements the Antiforgery logging filter configuration that the issue describes needing documentation for.

---

Tips and commands

Interacting with Sourcery

• Trigger a new review: Comment @sourcery-ai review on the pull request.
• Continue discussions: Reply directly to Sourcery's review comments.
• Generate a GitHub issue from a review comment: Ask Sourcery to create an
  issue from a review comment by replying to it. You can also reply to a
  review comment with @sourcery-ai issue to create an issue from it.
• Generate a pull request title: Write @sourcery-ai anywhere in the pull
  request title to generate a title at any time. You can also comment
  @sourcery-ai title on the pull request to (re-)generate the title at any time.
• Generate a pull request summary: Write @sourcery-ai summary anywhere in
  the pull request body to generate a PR summary at any time exactly where you
  want it. You can also comment @sourcery-ai summary on the pull request to
  (re-)generate the summary at any time.
• Generate reviewer's guide: Comment @sourcery-ai guide on the pull
  request to (re-)generate the reviewer's guide at any time.
• Resolve all Sourcery comments: Comment @sourcery-ai resolve on the
  pull request to resolve all Sourcery comments. Useful if you've already
  addressed all the comments and don't want to see them anymore.
• Dismiss all Sourcery reviews: Comment @sourcery-ai dismiss on the pull
  request to dismiss all existing Sourcery reviews. Especially useful if you
  want to start fresh with a new review - don't forget to comment
  @sourcery-ai review to trigger a new review!

Customizing Your Experience

Access your dashboard to:

• Enable or disable review features such as the Sourcery-generated pull request
  summary, the reviewer's guide, and others.
• Change the review language.
• Add, remove or edit custom review instructions.
• Adjust other review settings.

Getting Help

• Contact our support team for questions or feedback.
• Visit our documentation for detailed guides and information.
• Keep in touch with the Sourcery team by following us on X/Twitter, LinkedIn or GitHub.

[sourcery-ai]

Hey - I've left some high level feedback:

• If the intent is to suppress DefaultAntiforgery logs across all providers, consider moving this override to the root Logging:LogLevel section instead of only under LgbFile so behavior is consistent between sinks.
• Using the full type name Microsoft.AspNetCore.Antiforgery.DefaultAntiforgery is very specific; consider targeting the broader category Microsoft.AspNetCore.Antiforgery if you want to suppress antiforgery logs from related components as well.

Prompt for AI Agents

Please address the comments from this code review:

## Overall Comments
- If the intent is to suppress `DefaultAntiforgery` logs across all providers, consider moving this override to the root `Logging:LogLevel` section instead of only under `LgbFile` so behavior is consistent between sinks.
- Using the full type name `Microsoft.AspNetCore.Antiforgery.DefaultAntiforgery` is very specific; consider targeting the broader category `Microsoft.AspNetCore.Antiforgery` if you want to suppress antiforgery logs from related components as well.

---

Sourcery is free for open source - if you like our reviews please consider sharing them ✨

• X
• Mastodon
• LinkedIn
• Facebook

_{Help me be more useful! Please click 👍 or 👎 on each comment and I'll use the feedback to improve your reviews.}

[Copilot]

Pull request overview

This PR addresses noisy Antiforgery-related log output by updating the logging package and adding a category-specific log-level override for the file logger configuration (fixes #8016).

Changes:

• Bump Longbow.Logging dependency from 10.0.0 to 10.0.1.
• Add a Logging:LgbFile:LogLevel rule to disable logging for Microsoft.AspNetCore.Antiforgery.DefaultAntiforgery.

Reviewed changes

Copilot reviewed 2 out of 2 changed files in this pull request and generated no comments.

File	Description
src/BootstrapBlazor.Server/BootstrapBlazor.Server.csproj	Updates Longbow.Logging to a newer patch version to support/align with the logging change.
src/BootstrapBlazor.Server/appsettings.json	Adds a file-logger category filter to suppress DefaultAntiforgery logs.

---

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

[codecov]

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 100.00%. Comparing base (4cdc748) to head (a2a0c32).
⚠️ Report is 1 commits behind head on main.

Additional details and impacted files

@@            Coverage Diff            @@
##              main     #8017   +/-   ##
=========================================
  Coverage   100.00%   100.00%           
=========================================
  Files          766       766           
  Lines        34123     34123           
  Branches      4692      4692           
=========================================
  Hits         34123     34123           

Flag	Coverage Δ
BB	100.00% <ø> (?)

Flags with carried forward coverage won't be shown. Click here to find out more.

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
• 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.