Better support for navigator parameters
Nobody has claimed this yet.
- Dominant language
- Java
- Stars
- 1.8k
- Forks
- 717
- Avg merge
- 2d 6h
- Merged PRs (30d)
- 3
Description
At this moment the only way to pass parameters to a view is to use ViewChangeEvent's method getParameters() and parse the string it returns.
Being accustomed to JSR 311 (JAX-RS) and its URI Path Templates I'd find very useful a similar approach in Vaadin, like many other SPA frameworks do.
One will then be able to have fragments like users/{id}/profile attached to the UserProfile view and users/{id}/preferences to the UserPreferences view, both able to retrieve the id parameter with something like ViewChangeEvent.getParameter("id") or getParameters().get("id").
This will also be very useful in case of hierarchical navigators, as proposed in https://github.com/vaadin/framework/issues/8220.
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 by reviewing ViewChangeEvent.getParameters() and the hierarchical navigator proposal in issue 8220. Define how URI path templates and named parameters should work for views, including hierarchical navigation, and confirm that a view can retrieve parameters such as id without parsing a string.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java
- Domain
- frontend, web-dev
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 25/100