-
Notifications
You must be signed in to change notification settings - Fork 946
fix(Link): define NuxtLinkProps instead of importing from #app
#5491
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. Weβll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Merged
+53
β2
Merged
Changes from all commits
Commits
Show all changes
2 commits
Select commit
Hold shift + click to select a range
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
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
Oops, something went wrong.
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.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The
activeClassproperty is missing from theLinkPropsinterface definition, even though it's used throughout the component code. This will cause TypeScript errors when accessingprops.activeClass.View Details
π Patch Details
Analysis
Missing
activeClassproperty in LinkProps interfacesWhat fails: TypeScript error TS2551 when accessing
props.activeClassin components that use it but don't define it in the interface. TheLinkPropsinterface insrc/runtime/components/Link.vueandsrc/runtime/vue/components/Link.vuewas missing theactiveClass?: stringproperty despite the code accessing it on lines 126/128 and 165/167 respectively.How to reproduce:
Result: TypeScript compiler would report errors when accessing
props.activeClasson these components, even though the property is used in the template code viareactiveOmit(line 119/71) and in theuicomputed property (lines 126/100) andresolveLinkClassfunction (lines 165/176).Expected: The
LinkPropsinterface should includeactiveClass?: stringto match the code's usage and be consistent withsrc/runtime/inertia/components/Link.vuewhich already has this property defined.Fix applied: Added
activeClass?: stringproperty to theLinkPropsinterface in both:src/runtime/components/Link.vue(line 82)src/runtime/vue/components/Link.vue(line 51)This makes all three Link components consistent and resolves the TypeScript type error.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
activeClasslives inside RouterLinkProps