Help users apply compatibility mode in the right way
Nobody has claimed this yet.
- Dominant language
- Java
- Stars
- 186
- Forks
- 98
- PR merge metrics
- No merged PRs in 30d
Description
Spring Boot actively ignores web fragments which means that the flow-server-compatibility-mode dependency isn't automatically enabling compatibility mode. This is mentioned in the documentation but there's still a significant risk that users are struggling because they didn't notice the documentation.
To deal with this, Vaadin could explicitly look for the situation when flow-server-compatibility-mode is present (potentially by adding an additional marker to that package) and in case the property also isn't set, then either explicitly set it or throw an exception at startup.
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
No files, tests, or entry points are named. Start by tracing how Spring Boot handles the flow-server-compatibility-mode dependency and the compatibility-mode property, then clarify whether the intended result is automatic property setting or a startup exception. Done requires an agreed behavior for the dependency-present/property-absent case and coverage for that startup path.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java, spring, spring-boot
- Domain
- backend
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100