Merged
Conversation
Collaborator
Failing test suitesCommit: 2da9811 | About building and testing Next.js |
devjiwonchoi
approved these changes
Mar 28, 2026
eps1lon
force-pushed
the
sebbie/ftl/typed-links-cause
branch
from
050629f to
2da9811
Compare
Member
Author
|
Failures are unrelated |
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
3 participants
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.
Targetted at debugging (too) complex route types.
Helps debugging which route type was caused by which route file. This is especially helpful with non-trivial routes (route groups, breadcrumbs) and redirects/rewrites.
Redirect/rewrites won't have a helpful cause. For now the most helfpul info for me was knowing which file route it belongs to and if it's a redirect or not.
First commit is a refactor getting rid of intermediate arrays in favor of a more simpler programming model with for-loops and visited tracker.