perf(RequiredValidator): call GetLocalizerErrorMessage after validate failed

[AiYuZhen]

fix(RequiredValidator):优化 ValidationResult 生成代码

Summary of the changes (Less than 80 chars)

简单描述你更改了什么, 不超过80个字符；如果有关联 Issue 请在下方填写相关编号

优化 public override void Validate(object? propertyValue, ValidationContext context, List<ValidationResult> results) 方法，只有在验证不通过时才执行创建 ValidationResult 的相关格式化代码。

fixes #4997

Regression?

• Yes
• No

[If yes, specify the version the behavior has regressed from]

[是否影响老版本]

Risk

• High
• Medium
• Low

[Justify the selection above]

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

Bug Fixes:

• Fix a crash in RequiredValidator when a custom ErrorMessage is used with invalid formatting.

Summary by Sourcery

Bug Fixes:

• Optimize the Validate method to improve performance by generating ValidationResult only when necessary.

[sourcery-ai]

Reviewer's Guide by Sourcery

This pull request optimizes the RequiredValidator by generating ValidationResult objects only when validation fails. Previously, the code to format the error message and create the ValidationResult was executed regardless of the validation outcome. This change improves performance by avoiding unnecessary object creation and formatting when the validation succeeds.

Sequence diagram for optimized RequiredValidator validation flow

sequenceDiagram
    participant C as Client
    participant V as RequiredValidator
    participant VC as ValidationContext

    C->>+V: Validate(propertyValue, context, results)
    alt propertyValue is null
        V->>V: GetValidationResult(context)
        V->>VC: GetValidationResult(errorMessage)
        VC-->>V: ValidationResult
        V->>V: results.Add(ValidationResult)
    else propertyValue is empty string
        V->>V: GetValidationResult(context)
        V->>VC: GetValidationResult(errorMessage)
        VC-->>V: ValidationResult
        V->>V: results.Add(ValidationResult)
    else propertyValue is empty IEnumerable
        V->>V: GetValidationResult(context)
        V->>VC: GetValidationResult(errorMessage)
        VC-->>V: ValidationResult
        V->>V: results.Add(ValidationResult)
    end
    V-->>-C: void

Loading

File-Level Changes

Change	Details	Files
Optimize ValidationResult generation	Create a new GetValidationResult method in RequiredValidator to encapsulate the logic for creating ValidationResult objects. Move the logic for formatting the error message and creating the ValidationResult into the GetValidationResult method. Call the GetValidationResult method only when the validation fails. Add a new extension method GetValidationResult to ValidationContextExtensions to create a ValidationResult with the given error message and member names. Use the new GetValidationResult extension method in the RequiredValidator to simplify the code.	src/BootstrapBlazor/Validators/RequiredValidator.cs src/BootstrapBlazor/Extensions/ValidateContextExtensions.cs
Update project file	Update the project file to reflect the changes made in the code.	src/BootstrapBlazor/BootstrapBlazor.csproj

Assessment against linked issues

Issue	Objective	Addressed	Explanation
#4997	Handle custom RequiredAttribute with ErrorMessage containing custom placeholder {{Value}} without causing an exception during validation	✅
#4997	Adjust RequiredValidator's localization code execution timing to prevent errors when formatting ErrorMessage	✅
#4997	Ensure validation works correctly when using custom error messages with complex formatting	✅

Possibly linked issues

• perf(RequiredValidator): 数据合规性检查失败时调用 GetLocalizerErrorMessage 提高性能 #4997: The PR fixes the issue by optimizing the ValidationResult generation code to only format error messages when validation fails, preventing the exception described in the issue.

---

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.
• Generate a pull request title: Write @sourcery-ai anywhere in the pull
  request title to generate a 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. You can also use
  this command to specify where the summary should be inserted.

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.

[bb-auto]

Thanks for your PR, @AiYuZhen. Someone from the team will get assigned to your PR shortly and we'll get it reviewed.

[sourcery-ai]

Hey @AiYuZhen - I've reviewed your changes - here's some feedback:

Overall Comments:

• The System.Security.AccessControl using statement appears to be unused and can be removed.

Here's what I looked at during the review

• 🟢 General issues: all looks good
• 🟢 Security: all looks good
• 🟢 Testing: all looks good
• 🟢 Complexity: all looks good
• 🟢 Documentation: all looks good

---

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 100.00%. Comparing base (8080408) to head (2a3b559).
Report is 1 commits behind head on main.

Additional details and impacted files

@@            Coverage Diff            @@
##              main     #4996   +/-   ##
=========================================
  Coverage   100.00%   100.00%           
=========================================
  Files          630       630           
  Lines        27922     27928    +6     
  Branches      3996      3996           
=========================================
+ Hits         27922     27928    +6     

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

[ArgoZhang]

@sourcery-ai review

[sourcery-ai]

Hey @AiYuZhen - I've reviewed your changes and they look great!

Here's what I looked at during the review

• 🟢 General issues: all looks good
• 🟢 Security: all looks good
• 🟢 Testing: all looks good
• 🟢 Complexity: all looks good
• 🟢 Documentation: all looks good

---

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