bugfix: Fix direct navigation issue #988
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
Signed-off-by: Jared Scott <[email protected]>
even-wei
approved these changes
Dec 9, 2025
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.
Direct URL access to routes like /query, /lineage, and /checks was returning 404 errors because Next.js static export generated route.html files (e.g., query.html) while FastAPI's StaticFiles only looks for index.html inside directories.
Adding trailingSlash: true to next.config.js causes the build to generate index.html inside route directories (e.g., query/index.html), which FastAPI's StaticFiles with html=True can serve correctly.
PR checklist
What type of PR is this?
fix
What this PR does / why we need it:
Ensure direct access to lineage, query, or checklist does not 404
Which issue(s) this PR fixes:
N/A
Special notes for your reviewer:
Does this PR introduce a user-facing change?:
NONE