Skip to content

FluentSelect two-way binding help #1251

Answered by vnbaaij
paulpitchford asked this question in Q&A
Discussion options

You must be logged in to vote

Hi Paul,

OptionValue is indeed always a sting (we're looking at altering that for a future version). See also #1133 for more information

I think for your example you would need to change the code for the FluentSelect to have:

OptionValue="@(x => x.Id.ToString)"
@bind-SelectedOption="@SelectedOption"

where @SelectedOption is of type StandardsCategory

Replies: 1 comment 1 reply

Comment options

You must be logged in to vote
1 reply
@paulpitchford
Comment options

Answer selected by paulpitchford
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Category
Q&A
Labels
None yet
2 participants