Allow users to create a Page hierarchy inside the Pages directory #1561
Conversation
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
…is will support Inertia's advocated way of not constantly reloading the Layout component for Member Pages, for example.
|
We are releasing our new starter kits in 2 weeks so would rather address there if needed. |
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.
This will support Inertia's advocated way of not constantly reloading the Layout component for Member Pages, for example.
Currently, the Jetstream-created Pages, while being adaptable, are loaded from the "Pages/Team/...vue" directory, for example. If one has an Inertia page resolve function that loads and applies a page's layout based on page name prefix (e.g. "Members/Teams/...vue") then the hardcoded paths in the src/Http/Controllers/Inertia/...Controller.php files will not be able to find the pages inside the subdirectories.
This change allows users to set a page prefix so that pages are loaded from the correct subdirectory.
The default value is an empty string.