Better article for binding data to components
Nobody has claimed this yet.
- Dominant language
- AsciiDoc
- Stars
- 38
- Forks
- 225
- Avg merge
- 1d 4h
- Merged PRs (30d)
- 170
Description
Tell us about your request
Binding Data to Components article is missing the following:
- How to bind items to the
TreeGrid, in-memory and backend. - How to make an add-on to
DataProvider, either plain and hierarchical. - The article should have a laconic user-friendly name and url, e.g. "Data in Components", "/data-in-components". And this should be a top-level article on the same level as "Forms", because this is 99,9% use case in business applications.
Also can be done together with https://vaadin.com/docs/latest/flow/binding-data/data-provider to add more reasoning around data view concept.
If you think this issue is important, add a 👍 reaction to help the community and maintainers prioritize this issue.
Contributor guide
No contributing guide indexed for this repository
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 linked Binding Data to Components article at /flow/binding-data/data-provider. Document TreeGrid binding for in-memory and backend data, explain plain and hierarchical DataProvider add-ons, and assess the proposed title, URL, and top-level placement; done means these topics and the data view reasoning are covered in a user-friendly article.
Written by the indexing model from the issue text.
Assessment
- Domain
- documentation
- Issue type
- Documentation
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100