Skip to content

BUGFIX: Loosely compare values in isOptionSelected #27

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.

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

Merged
merged 1 commit into from
Dec 24, 2022

Conversation

kdambekalns
Copy link
Member

Make this method compares values "type unsafe", because due to the nature of web requests numbers and strings cannot really be distinguished. This leads to false negatives if option values are given as numbers but incoming data is a string.

Fixes #26

Make this method compares values "type unsafe", because due to the
nature of web requests numbers and strings cannot really be
distinguished. This leads to false negatives if option values are
given as numbers but incoming data is a string.

Fixes neos#26
@kdambekalns kdambekalns self-assigned this Dec 22, 2022
@mhsdesign
Copy link
Member

wondering if its breaking? if not 👍

@kdambekalns
Copy link
Member Author

wondering if its breaking?

Who knows… 😎

@kdambekalns
Copy link
Member Author

I hope @GuangHa can test this in a real-world project…

@mhsdesign mhsdesign merged commit 98ddc8d into neos:master Dec 24, 2022
@daniellienert
Copy link
Member

@kdambekalns Uh just realized, target on master was probably not intended?

@kdambekalns
Copy link
Member Author

Uh just realized, target on master was probably not intended?

@daniellienert There aren't any other release branches…

@kdambekalns kdambekalns deleted the bugfix/26-select-numeric-options branch January 4, 2023 10:31
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Rendering of radio and single-select
4 participants