Support for type-hinting shared Page Props #2636
Merged
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 allows you to type-hint shared page props in a global type definition file, for example,
resources/js/types/globals.d.ts.Now the shared page props are automatically type-hinted throughout the app when you use
usePage().In the example above,
successMessagewill be typed asstring | undefined. In Svelte and Vue, this also works in the template.You can still pass an interface to
usePage()for page-specific props, which will automatically be merged with the declaredsharedPageProps.In this case,
postTitleswill be typed asstring[].For reference, previously, you could already partially do this by extending the
PagePropsinterface.The problem with this approach is that the shared page props are overwritten when you pass a specific interface to
usePage().This was originally planned in PR #2549, but I decided to split it up into multiple PRs for clarity.