Preserve Svelte return URLs and resolve runtime paths - #2566
Merged
Conversation
Codex Review SummaryThis comment shows the latest Codex review activity on this pull request.
ℹ️ About Codex in GitHubYour team has set up Codex to review pull requests in this repo. Reviews are triggered when you
Codex reacts with 👀 while any review is running, comments if it has suggestions, and reacts with 👍 once all reviews finish with no findings. |
ejsmith
changed the title
|
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
1 participant
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.
Preserves query parameters and fragments when the Svelte auth guard sends a user to login, so notification destinations, verification tokens, and filters survive authentication or session expiry.
Replaces the remaining 10 hardcoded runtime
/nextreferences with SvelteKitresolvein assistant navigation, assistant link handling, and telemetry. Root-hosted assistant links preserve external destinations and existing Markdown. Hosting configuration, backend link producers, and historical redirects remain part of the UI removal plan.Validation: 40 focused unit tests and the local Exie navigation browser test passed; Svelte check (zero errors/warnings), formatting, lint, and production build passed. The existing login/session-expiry browser regression remains included.
No public API changes or new base-path configuration.