Fix usePage() null object error in Vue 3 adapter
#1530
Merged
Conversation
This file contains 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
reinink
changed the title
usePage() null object error in Vue 3 adapter
|
Hey, thanks for putting that together! |
|
@reinink Hey, thanks for the explanation and fast response! |
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.
follow-up fix for #1469, as proposed by @reinink
I have tested this with a local build and all is working as expected again.
--
@reinink comments:
This PR fixes situations where the
usePage()hook is used before Inertia has been initialized — for example in 3rd party libraries. In these situations the internalpageref in the root<App>component is stillnull, which results in an error because it's trying to findprops,url,component, etc. properties on anullobject.