Spring Security docs for Hilla implies that a custom routes.tsx is needed
Nobody has claimed this yet.
- Dominant language
- AsciiDoc
- Stars
- 38
- Forks
- 225
- Avg merge
- 1d 4h
- Merged PRs (30d)
- 170
Description
Looking at https://vaadin.com/docs/latest/hilla/guides/security/spring-login, you may get the impression that you have to stop using the FS router and start defining routes manually in routes.tsx to get proper access control. This should be clarified.
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 by reading the Spring Security login page at the linked Hilla documentation URL and inspect its guidance around the FS router and routes.tsx. Clarify the routing guidance so readers can understand whether a custom routes.tsx is required for access control, then verify the rendered documentation no longer implies that it is mandatory.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- spring
- Domain
- documentation
- Issue type
- Documentation
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 48/100