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.

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

fix!: throw when setting value that is not present in key mapper #6273

Closed
wants to merge 1 commit into from

Conversation

vursen
Copy link
Contributor

@vursen vursen commented May 6, 2024

Description

Setting values that aren't present in the key mapper shouldn't be allowed, as they cannot be represented on the client-side.

Related to vaadin/flow#19310

Fixes #6605

Type of change

  • Bugfix

@vursen vursen changed the title fix!: throw when setting value that is not present in key mapper fix!: throw when setting values that are not present in key mapper May 6, 2024
Copy link

sonarcloud bot commented May 6, 2024

Quality Gate Passed Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
No data about Coverage
0.0% Duplication on New Code

See analysis details on SonarCloud

@vursen vursen changed the title fix!: throw when setting values that are not present in key mapper fix!: throw when setting value that is not present in key mapper May 6, 2024
@vursen
Copy link
Contributor Author

vursen commented May 28, 2024

ComboBox is another candidate for this fix.

@yuriy-fix
Copy link
Contributor

@vursen, please create a ticket for this PR to address. Discussion could be started within the ticket.

@vursen
Copy link
Contributor Author

vursen commented Sep 3, 2024

please create a ticket for this PR to address. Discussion could be started within the ticket.

Thanks, done.

@vursen vursen closed this Sep 3, 2024
@vursen vursen reopened this Sep 3, 2024
@vursen vursen closed this Sep 5, 2024
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.

Server should not allow setting values that are not in data provider
2 participants