Skip to content

FluentSelect: Fix ValueChanged fired twice #382

FluentSelect: Fix ValueChanged fired twice

FluentSelect: Fix ValueChanged fired twice #382

Triggered via pull request October 5, 2023 22:20
Status Failure
Total duration 5m 59s
Artifacts
This run and associated checks have been archived and are scheduled for deletion. Learn more about checks retention

deploy_preview.yml

on: pull_request
Build and deploy Demo site
5m 49s
Build and deploy Demo site
Close Pull Request Job
0s
Close Pull Request Job
Fit to window
Zoom out
Zoom in

Annotations

3 warnings
Build and deploy Demo site: examples/Demo/Shared/Pages/Lab/IssueTester.razor#L24
This async method lacks 'await' operators and will run synchronously. Consider using the 'await' operator to await non-blocking API calls, or 'await Task.Run(...)' to do CPU-bound work on a background thread.
Build and deploy Demo site: examples/Demo/Shared/Pages/Lab/IssueTester.razor#L24
This async method lacks 'await' operators and will run synchronously. Consider using the 'await' operator to await non-blocking API calls, or 'await Task.Run(...)' to do CPU-bound work on a background thread.
Build and deploy Demo site: examples/Demo/Shared/Pages/Lab/IssueTester.razor#L24
This async method lacks 'await' operators and will run synchronously. Consider using the 'await' operator to await non-blocking API calls, or 'await Task.Run(...)' to do CPU-bound work on a background thread.