fix(AutoComplete): trigger OnValueChanged when the Value changed

[ArgoZhang]

Link issues

link #5479
link #5480

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 Copilot

This pull request includes updates to the versioning, improvements to the AutoComplete component, and some code cleanups. The most important changes include updating the project version, modifying the TriggerFilter method, and refining the JavaScript functions for the AutoComplete component.

Version update:

• src/BootstrapBlazor/BootstrapBlazor.csproj: Updated the project version from 9.4.3-beta02 to 9.4.3-beta03.

Improvements to AutoComplete component:

• src/BootstrapBlazor/Components/AutoComplete/AutoComplete.razor.cs: Modified the TriggerFilter method to call await TriggerChange(val) instead of StateHasChanged().

JavaScript refinements:

• src/BootstrapBlazor/Components/AutoComplete/AutoComplete.razor.js: Removed unnecessary condition check for useInput in the init function.
• src/BootstrapBlazor/Components/AutoComplete/AutoComplete.razor.js: Removed the menu variable and added an event handler cleanup for change event in the dispose function.

Summary by Sourcery

Fixes an issue where the AutoComplete component's OnValueChanged event was not triggered when the value changed. This is achieved by calling TriggerChange(val) instead of StateHasChanged() in the TriggerFilter method. Additionally, this PR includes minor JavaScript code cleanup and a version update.

Bug Fixes:

• Fixes an issue where the AutoComplete component's OnValueChanged event was not triggered when the value changed.
• Removes an unnecessary condition check for useInput in the init function of the AutoComplete component's JavaScript.
• Removes the menu variable and adds an event handler cleanup for the change event in the dispose function of the AutoComplete component's JavaScript.

Enhancements:

• Updates the project version to 9.4.3-beta03.

[sourcery-ai]

Reviewer's Guide by Sourcery

This pull request includes updates to the versioning, improvements to the AutoComplete component, and some code cleanups. The most important changes include modifying the TriggerFilter method, and refining the JavaScript functions for the AutoComplete component.

Updated class diagram for AutoComplete component

classDiagram
    class AutoComplete {
        -List<string> _filterItems
        -int? DisplayCount
        +Task TriggerFilter(string val)
        +Task TriggerChange(string val)
    }
    note for AutoComplete "TriggerFilter method now calls TriggerChange instead of StateHasChanged()"

Loading

File-Level Changes

Change	Details	Files
The TriggerFilter method was modified to call TriggerChange instead of StateHasChanged.	Replaced StateHasChanged() with await TriggerChange(val) in the TriggerFilter method.	src/BootstrapBlazor/Components/AutoComplete/AutoComplete.razor.cs
Refined JavaScript functions for the AutoComplete component.	Removed unnecessary condition check for useInput in the init function. Removed the menu variable and added an event handler cleanup for the change event in the dispose function.	src/BootstrapBlazor/Components/AutoComplete/AutoComplete.razor.js
The project version was updated.	Updated the project version from 9.4.3-beta02 to 9.4.3-beta03.	src/BootstrapBlazor/BootstrapBlazor.csproj

Assessment against linked issues

Issue	Objective	Addressed	Explanation
#5479	The OnValueChanged event of the AutoComplete component should trigger when the input value changes.	✅

Possibly linked issues

• bug(AutoComplete): trigger OnValueChanged when the Value changed #5479: The PR fixes the issue by modifying the TriggerFilter method to call TriggerChange, addressing the problem of the ValueChanged event not firing.

---

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!
• Generate a plan of action for an issue: Comment @sourcery-ai plan on
  an issue to generate a plan of action for it.

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:

Overall Comments:

• The removal of the useInput check in AutoComplete.razor.js seems correct, but could use a comment explaining why it's no longer needed.
• Consider adding a brief explanation of why TriggerChange is preferred over StateHasChanged in the TriggerFilter method.

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 (38dc157) to head (2952aca).
Report is 1 commits behind head on main.

Additional details and impacted files

@@            Coverage Diff            @@
##              main     #5485   +/-   ##
=========================================
  Coverage   100.00%   100.00%           
=========================================
  Files          649       649           
  Lines        29541     29541           
  Branches      4163      4163           
=========================================
  Hits         29541     29541           

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