feat(ValidateForm): use IOptionsMonitor option

[ArgoZhang]

Link issues

fixes #6554

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

Use IOptionsMonitor instead of IOptions for retrieving BootstrapBlazor and localization options to ensure runtime updates are reflected.

Bug Fixes:

• Fix feat(ValidateForm): use IOptionsMonitor option #6554 by ensuring option changes take effect at runtime

Enhancements:

• Replace IOptions with IOptionsMonitor in InputNumber and ValidateForm components and update usages to CurrentValue

[sourcery-ai]

Reviewer's Guide

This PR transitions form validation and input number components to use IOptionsMonitor instead of IOptions to support dynamic option changes, updating references from Value to CurrentValue accordingly.

File-Level Changes

Change	Details	Files
Switched InputNumber component to IOptionsMonitor for step configuration	Injected IOptionsMonitor instead of IOptions Replaced StepOption.Value.GetStep() with StepOption.CurrentValue.GetStep()	src/BootstrapBlazor/Components/InputNumber/BootstrapInputNumber.razor.cs
Switched ValidateForm component to IOptionsMonitor for localization options	Injected IOptionsMonitor instead of IOptions Replaced Options.Value.ResourceManagerStringLocalizerType with Options.CurrentValue.ResourceManagerStringLocalizerType	src/BootstrapBlazor/Components/ValidateForm/ValidateForm.razor.cs

Assessment against linked issues

Issue	Objective	Addressed	Explanation
#6554	Update ValidateForm to use IOptionsMonitor instead of IOptions for options injection.	✅

Possibly linked issues

• feat(ValidateForm): use IOptionsMonitor option #6554: The PR implements the feature described in the issue, changing IOptions to IOptionsMonitor.

---

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 @ArgoZhang - I've reviewed your changes - here's some feedback:

• Consider renaming the injected IOptionsMonitor properties (StepOption and Options) to more descriptive names like StepOptionsMonitor or LocalizationOptionsMonitor, since they’re now monitors rather than simple options.
• If you’re switching to IOptionsMonitor for live updates, make sure to subscribe to OnChange or otherwise trigger component re-renders when the monitored options change so UI updates correctly.
• If you don’t actually need real-time option reloads at runtime, IOptionsSnapshot might be a lighter alternative that still gives you up‐to‐date values per scope without the overhead of a full monitor.

Prompt for AI Agents

Please address the comments from this code review:
## Overall Comments
- Consider renaming the injected IOptionsMonitor properties (StepOption and Options) to more descriptive names like StepOptionsMonitor or LocalizationOptionsMonitor, since they’re now monitors rather than simple options.
- If you’re switching to IOptionsMonitor for live updates, make sure to subscribe to OnChange or otherwise trigger component re-renders when the monitored options change so UI updates correctly.
- If you don’t actually need real-time option reloads at runtime, IOptionsSnapshot might be a lighter alternative that still gives you up‐to‐date values per scope without the overhead of a full monitor.

---

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.}

[codecov]

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 99.93%. Comparing base (096d3a7) to head (860181d).
⚠️ Report is 1 commits behind head on main.

Additional details and impacted files

@@           Coverage Diff           @@
##             main    #6555   +/-   ##
=======================================
  Coverage   99.93%   99.93%           
=======================================
  Files         715      715           
  Lines       31471    31471           
  Branches     4444     4444           
=======================================
  Hits        31451    31451           
  Misses         15       15           
  Partials        5        5           

Flag	Coverage Δ
BB	99.93% <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.