Repository navigation
feat: Add Binder.refreshFields() - #13535
Merged
Merged
Conversation
Contributor
knoobie
reviewed
Apr 13, 2022
taefi
suggested changes
Apr 19, 2022
Co-authored-by: Soroosh Taefi <taefi.soroosh@gmail.com>
Contributor
|
@tarekoraby please merge current master to your branch |
|
Kudos, SonarCloud Quality Gate passed!
|
mshabarov
approved these changes
Apr 27, 2022
taefi
approved these changes
Apr 27, 2022
Collaborator
|
This ticket/PR has been released with Vaadin 23.1.0.alpha4 and is also targeting the upcoming stable 23.1.0 version. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.








In situations when a bean
foothat is bound to a binder has one its properties changed on the server-side, one currently needs to reset the binding to that bean in order for the new property value to be reflected on the fields.So if I have
Then I would need to call
binder.setBean(foo)again for the value to be reflected on the field associated with the propertybar.This usage is, however, not obvious to the user as what they want to do is only update the fields associated with the binder in order for them to reflect the updated state of the bean. (plus there is a very minor wastefulness in calling
binder.setBean(foo)again as that removes the same bean only to add it again).This PR adds a
Binder.refreshFields()API to match the intention of the user in those use cases.