Skip to content

fix: switch overview range locally instead of pushing navigation - #4

Merged
stv1024 merged 1 commit into
stv1024:mainfrom
ChtJT:overview-range-local-state
Oct 23, 2026
Merged

stv1024 merged 1 commit into
stv1024:mainfrom
ChtJT:overview-range-local-state

Conversation

@ChtJT

@ChtJT ChtJT commented Oct 16, 2026

Copy link
Copy Markdown
Contributor

openScreen is router.push in the host, so every range-button click stacked a new history entry. The SDK has no replace/setParams, so the range now lives in component state seeded from params; the title goes static because a param-derived title goes stale after local switching.

openScreen is router.push in the host, so every range-button click
stacked a new history entry. The SDK has no replace/setParams, so the
range now lives in component state seeded from params; the title goes
static because a param-derived title goes stale after local switching.

Generated with [Devin](https://devin.ai)

Co-Authored-By: Devin <158243242+devin-ai-integration[bot]@users.noreply.github.com>
@stv1024

stv1024 commented Oct 23, 2026

Copy link
Copy Markdown
Owner

Thanks for the clear report and the fix, and sorry for the slow reply. Paseo 0.12 still has no replace or setParams for screens, so local state is the right approach. Merging. It will ship in the next release.

@stv1024
stv1024 merged commit ba1af4a into stv1024:main Oct 23, 2026
3 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants