perf(LocalizerString): use FrozenSet improve performance

[ArgoZhang]

use FrozenSet improve performance

Summary of the changes (Less than 80 chars)

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

Description

fixes #5033

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

Improve the performance of LocalizerString by using FrozenSet.

New Features:

• Add a new API to get all localized strings from a service.

Enhancements:

• Use FrozenSet to improve the performance of LocalizerString.

[sourcery-ai]

Reviewer's Guide by Sourcery

This PR improves the performance of the LocalizerString component by using FrozenSet instead of HashSet in .NET 8 and above. It also refactors the code to improve readability and maintainability.

Sequence diagram for localized string retrieval

sequenceDiagram
    participant Client
    participant JsonStringLocalizer
    participant CacheManager
    Client->>JsonStringLocalizer: Get localized string
    JsonStringLocalizer->>CacheManager: GetAllStringsByTypeName()
    alt NET 8.0 or greater
        CacheManager-->>JsonStringLocalizer: Return FrozenSet
    else Earlier versions
        CacheManager-->>JsonStringLocalizer: Return HashSet
    end
    JsonStringLocalizer->>JsonStringLocalizer: GetValueFromCache()
    JsonStringLocalizer-->>Client: Return localized value

Loading

Class diagram showing the localization data structure changes

classDiagram
    class CacheManager {
        +GetAllStringsByTypeName(Assembly, string) FrozenSet~LocalizedString~
        +GetJsonStringByTypeName(JsonLocalizationOptions, Assembly, string, string?, bool) FrozenSet~LocalizedString~
        +GetAllStringsFromResolve(bool) FrozenSet~LocalizedString~
    }
    class JsonStringLocalizer {
        -GetValueFromCache(FrozenSet~LocalizedString~, string) string?
    }
    note for CacheManager "NET8_0_OR_GREATER: Uses FrozenSet
Other versions: Uses HashSet"
    JsonStringLocalizer ..> CacheManager: uses

Loading

File-Level Changes

Change	Details	Files
Use FrozenSet to improve performance	Replaced HashSet with FrozenSet for storing localized strings in .NET 8 and above. Updated methods to handle FrozenSet instead of HashSet. Added conditional compilation directives (#if NET8_0_OR_GREATER) to support both .NET 8 and older versions.	src/BootstrapBlazor/Services/CacheManager.cs src/BootstrapBlazor/Localization/Json/JsonStringLocalizer.cs src/BootstrapBlazor/Utils/Utility.cs src/BootstrapBlazor.Server/Extensions/CacheManagerExtensions.cs
Refactor code for better readability and maintainability	Simplified the logic for retrieving localized strings. Removed unnecessary null checks. Improved the naming of variables and methods.	src/BootstrapBlazor/Services/CacheManager.cs src/BootstrapBlazor/Extensions/LocalizationOptionsExtensions.cs src/BootstrapBlazor/Localization/Json/JsonStringLocalizer.cs
Update GetJsonLocalizationOption method's access modifier	Changed the access modifier of the GetJsonLocalizationOption method from public to private.	src/BootstrapBlazor/Services/CacheManager.cs
Fix a bug in Textarea and Display components	Fixed a bug where the closing tag for Textarea and Display components was missing.	src/BootstrapBlazor/Utils/Utility.cs

Assessment against linked issues

Issue	Objective	Addressed	Explanation
#5033	Use FrozenSet to improve performance	✅

Possibly linked issues

• perf(LocalizerString): use FrozenSet improve performance #5033: The PR addresses the issue by implementing the suggested FrozenSet usage.
• perf(LocalizerString): use FrozenSet improve performance #5033: The PR fixes the issue mentioned by updating the usage of collections and potentially resolving the endless loop.

---

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.

[sourcery-ai]

Hey @ArgoZhang - 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.}

[codecov]

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 100.00%. Comparing base (b917fd3) to head (e36a111).
Report is 1 commits behind head on main.

Additional details and impacted files

@@            Coverage Diff            @@
##              main     #5034   +/-   ##
=========================================
  Coverage   100.00%   100.00%           
=========================================
  Files          631       631           
  Lines        27961     27951   -10     
  Branches      4007      4006    -1     
=========================================
- Hits         27961     27951   -10     

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