Update info on how UI expiration works after Beacon API
Nobody has claimed this yet.
- Dominant language
- AsciiDoc
- Stars
- 38
- Forks
- 225
- Avg merge
- 1d 4h
- Merged PRs (30d)
- 170
Description
The UI expiration section should be updated to reflect that Flow now uses Beacon API to instantly detect when a UI is closed and clean up this UI (unless @PreserveOnRefresh is being used). See https://github.com/vaadin/flow/pull/16657.
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
Read the UI expiration section in the linked Vaadin application-lifecycle documentation and review Flow pull request 16657 for the Beacon API behavior. Update the section to explain immediate cleanup when a UI closes, including the exception for @PreserveOnRefresh; the documentation should match the current behavior.
Written by the indexing model from the issue text.
Assessment
- Domain
- documentation
- Issue type
- Documentation
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Stale
- Clarity
- Clearly specified
- Newbie friendliness
- 65/100