test(Lookup): add Select/Display Lookup test

[ArgoZhang]

add Select/Display Lookup test

Summary of the changes (Less than 80 chars)

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

Description

fixes #4984 #4985

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

Tests:

• Added a unit test to verify the functionality of the Lookup component with pre-defined lookup items.

[sourcery-ai]

Reviewer's Guide by Sourcery

This pull request adds a new unit test for the Select/Display Lookup feature. It verifies the lookup functionality in the EditorForm and Display components. It also includes updates to the Display component to handle lookup values correctly.

Sequence diagram for Display component value formatting

sequenceDiagram
    participant Display as Display Component
    participant Lookup as Lookup Service
    participant Formatter as Value Formatter

    Display->>Display: FormatValueString()
    Display->>Display: Get Value.ToString()
    Display->>Lookup: GetLookup()
    alt Lookup exists
        Lookup-->>Display: Return lookup value
        Display->>Formatter: Format with lookup value
    else No lookup
        Display->>Display: Return original string
    end
    Note over Display: Return formatted string or empty

Loading

Class diagram for Display component changes

classDiagram
    class Display {
        -Func~TValue, string~ _arrayConvertToString
        -Func~TValue, string~ _enumerableConvertToString
        +FormatValueString() Task~string~
        +ArrayConvertToString(TValue value) string
    }
    note for Display "Fixed variable naming and
value handling in FormatValueString"

Loading

File-Level Changes

Change	Details	Files
Added a unit test for Lookup in EditorForm	Created a new test method Lookup_Ok to verify the lookup functionality in EditorForm component. Added test case to check if the select component has the correct number of items.	test/UnitTest/Components/EditorFormTest.cs
Updated Display component to handle lookup values	Modified FormatValueString method to handle lookup values correctly. Added a new test case to DisplayTest to verify the lookup functionality with LookupServiceKey. Added a test case to DisplayTest to verify the lookup functionality with Lookup parameter.	src/BootstrapBlazor/Components/Display/Display.razor.cs test/UnitTest/Components/DisplayTest.cs
Minor updates to Display.razor.cs	Renamed _arrayConvertoString to _arrayConvertToString.	src/BootstrapBlazor/Components/Display/Display.razor.cs
No changes related to packaging		src/BootstrapBlazor/BootstrapBlazor.csproj

Assessment against linked issues

Issue	Objective	Addressed	Explanation
#4985	Add tests for the Select/Display Lookup component	✅

---

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 (20501e9) to head (7d10b4a).
Report is 580 commits behind head on main.

Additional details and impacted files

@@            Coverage Diff             @@
##             main     #4986     +/-   ##
==========================================
  Coverage   99.99%   100.00%             
==========================================
  Files         575       630     +55     
  Lines       25016     28073   +3057     
  Branches     3639      4025    +386     
==========================================
+ Hits        25015     28073   +3058     
+ Partials        1         0      -1     

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