FluentSelect two-way binding help #1251
Answered
by
vnbaaij
paulpitchford
asked this question in
Q&A
-
Beta Was this translation helpful? Give feedback.
Answered by
vnbaaij
Jan 2, 2024
Replies: 1 comment 1 reply
-
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
where |
Beta Was this translation helpful? Give feedback.
1 reply
Answer selected by
paulpitchford
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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:where
@SelectedOption
is of typeStandardsCategory