fix(queryParams): Improve TypeScript strict compatibility (follow-up to PR #106) #118
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.
This PR provides a complementary fix to PR #106 to ensure full compatibility with
TypeScript strict mode (including vue-tsc and isolatedModules).
PR #106 already improves nested query parameter handling, but the generated
queryParamsfunction still triggers TypeScript strict errors such as:These errors appear because
QueryParamsis a recursive union type, and TypeScriptrequires explicit narrowing before indexing or branching on values.
✔ What this PR fixes
✔ Why this matters
Wayfinder generates
.tsfiles that are imported into other generated files viarelative imports.
Because of that, developers cannot exclude the generated file from TypeScript
compilation, and strict mode compilation fails.
This fix ensures Wayfinder works out-of-the-box in modern TS setups.
🔗 Related