FieldBinder not compatible with Vaadin Designer
Nobody has claimed this yet.
- Dominant language
- Java
- Stars
- 1.8k
- Forks
- 717
- Avg merge
- 2d 6h
- Merged PRs (30d)
- 3
Description
Current FieldBinder in Vaadin 8.0 is trying to map components to fields (class) based on caption of component. This is causing issue with Vaadin Designer where only correct mapping is the name of component.
Steps
- Create new design with Vaadin Designer
- Have one component with name "add" and then another component with caption "add"
- Try to use design in your application
Expected outcome
Only the component with name "add" should be mapped to field. Design should load correctly.
Actual outcome
Initialisation of design fails as field binder is trying to pair also the other component to same field.
Based on Vaadin Design team they are the only customer of this functionality (I have no idea if that is true), so they asked to file bug for framework.
Issue is in FieldBinder.bindField method
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 at the FieldBinder.bindField method named in the issue and reproduce the Vaadin Designer steps with components whose name and caption both equal "add". Confirm that only the component named "add" is mapped and that the design loads without an initialization failure.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java
- Domain
- frontend
- Issue type
- Bug
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Stale
- Clarity
- Clearly specified
- Newbie friendliness
- 55/100