ix: resolve wiki breadcrumb crashes and browser redirect loop #346#413
Open
shivani11jadhav wants to merge 2 commits into
Open
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.
📝 Description
This PR addresses and completely resolves #346 by refactoring the local state architecture of the Wiki/Roadmap deep sub-pages into a modern, query-driven routing system. This fixes the client-side route crashes, state desynchronization, and the infinite back-navigation redirect loops.
🛠️ Changes Made
useStatehook foractiveArticleinsidesrc/app/wiki/page.tsxwith Next.js App Router's dynamic hooks (useSearchParamsanduseRouter).router.push('/wiki?article=id', { scroll: false }). This registers genuine browser history snapshots, fixing back-navigation gracefully.??) across all breadcrumb extraction nodes and header text layouts to secure the interface from rendering crashes if invalid strings are queried.<Suspense>boundary to fulfill the Next.js static asset build criteria smoothly.🧪 Verification & Testing
npx tsc --noEmit)./wiki?article=setup) successfully loads the targeted article content on mounting.GSSoC '26 Contributor. Please review and merge this patch! 🙌