Repository navigation
Toolify: resync saved-result share link when user switches locale or tool - #98
Merged
appdevelopsk merged 3 commits intoNov 15, 2026
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Follow-up to safe sharing fixes #97: main's
ShareBarused an effect with an empty dependency list ([]), so on client navigation between locales/tools without remounting, its shareable-result button (?s=state) could remain stale until a separate history event. The effect now resynchronizes whenurlorslugchanges while preserving all listener cleanup, tracked social share URLs, safe copyable embeds and native share cancellation behavior.Added 2 Node source-contract tests verifying the current
URLSearchParamsread and the three listeners/unlisteners, plus integration with the existing safe embed and attribution. Prebuild runs the test. Exact branch source was fetched and verified against 12 integration contracts (12/12). Native Next/Vitest, browser locale navigation and VPS deployment not verified; no uplift claim. No GitHub Actions triggered or analytics event schema changed.