Updating bean in Binder clears component error
Open
Nobody has claimed this yet.
documentation
Stale
- Dominant language
- Java
- Stars
- 1.8k
- Forks
- 717
- Avg merge
- 2d 6h
- Merged PRs (30d)
- 3
Description
- Vaadin Framework version 8.5.1
Opposite case of https://github.com/vaadin/framework/issues/11091 :
If use setComponentError() to set an error message for a component and then use a binding to update the bean, the error is never shown. It's not strictly speaking a bug, but can be confusing like in #11091 . This could also be documented in JavaDoc, perhaps in Binder::bind.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with the Binder::bind entry point and reproduce the reported sequence: set a component error, then update the bean through a binding. Document the resulting behavior in the Binder::bind JavaDoc; done means the documentation clearly explains when the component error is shown.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java
- Domain
- documentation
- Issue type
- Documentation
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 48/100