Vaadin Flow 24.2.8
Changes since 24.2.7
Fixes
-
Remove caching of AppShellConfigurator classes to fix injection (#18603)
Commit · Pull request · Issue -
Allow moving node to another tree after removeFromTree call (#18486)
Commit · Pull request · IssueEnables moving a component to another UI by just calling Element.removeFromTree() and then adding the component to the other UI.
-
Binder validation fixes (#18535)
Commit · Pull request · Issues 18163, 4988, 17515Changes:
- Once
Binder.handleFieldValueChangeruns for a binding whenreadBeanwas used, the whole binder will be silently validated also.BinderValidationStatusHandleris called like before (only contains status from changed binding), butStatusChangeEventis now fired considering all bindings and if possible bean validators as well. - Once
Binder.handleFieldValueChangeruns for a binding whensetBeanwas used,doWriteIfValidwill validate all bindings, not only the changed ones. This prevents writing an invalid bean in cases where one or more of the initial values are in invalid state (but not marked as such sincesetBeanresets validation status), but they have not been changed from their initial value(s). - Calling
setAsRequiredEnabledwith a changed value no longer triggers validation, since that validation is now handled elsewhere when needed as stated above. - Minor Javadoc fixes, aligning Javadocs with code.
- Once
-
Propagate all request parameter to location in eagerServerLoad mode (#18489) (CP: 24.2)
Commit · Pull request · Issue
-
Replace 'blacklist' and 'whitelist' with 'blocked' and 'allowed' (#18405)
Commit · Pull request · IssueMark the existing methods as deprecated and introduce methods with new names. Fall back to the old configuration properties if the new ones aren't used.