-
Notifications
You must be signed in to change notification settings - Fork 176
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
Binder.removeBinding issue #5384
Comments
The first thing i would suggest you is updating your flow version to the latest ones, ( if you are using flow separately, the version number is |
Looks like this is a bug in Refer to vaadin/framework#11280 (comment) to fix it: The issue is located in
it's missing: |
In Vaadin flow 1.0.5, I have several fields bound to a Binder instance. When I remove a binding (where there are still other bound properties) it is calling unbind. It seems like it should only call unbind when the count of bound properties is zero? Here is the code.
I end up receiving errors after I remove the binding
java.lang.NullPointerException: This Binding is no longer attached to a Binder
at java.base/java.util.Objects.requireNonNull(Objects.java:246) ~[na:na]
at com.vaadin.flow.data.binder.Binder$BindingImpl.validate(Binder.java:1027) ~[flow-data-1.0.5.jar:na]
from my other bound fields that are still using the binding.
Perhaps I'm misunderstanding how this should work? See vaadin/framework#11280 for reference
The text was updated successfully, but these errors were encountered: