Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Triggering of after-binding-logic with @bind:after instead of custom ValueChanged handler #371

Closed
hakenr opened this issue Sep 10, 2022 · 0 comments
Closed

Triggering of after-binding-logic with @bind:after instead of custom ValueChanged handler #371

hakenr opened this issue Sep 10, 2022 · 0 comments
Labels
net7
Milestone
Backlog

Comments

@hakenr
Copy link
Member

hakenr commented Sep 10, 2022 •
edited
Loading

Instead of splitting @bind to Value and ValueChanged, use @bind:after modifier for triggering the added ValueChanged logic.
https://devblogs.microsoft.com/dotnet/asp-net-core-updates-in-dotnet-7-preview-7/#blazor-data-binding-get-set-after-modifiers

(both components code + DEMOs in doc)
@hakenr hakenr added the net7 label Sep 10, 2022
@hakenr hakenr added this to the Backlog milestone Sep 10, 2022
hakenr added a commit that referenced this issue Jan 7, 2024
@hakenr
#371 Triggering of after-binding-logic with @Bind:after instead of cu…
ccd64b2 
…stom ValueChanged handler
@hakenr hakenr closed this as completed Jan 7, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
net7
Projects
None yet
Milestone
Backlog
Development

No branches or pull requests
1 participant
@hakenr