-
-
Notifications
You must be signed in to change notification settings - Fork 1
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
UX Improvement: See if the Blade view directory can easily be changed #65
Comments
Actually not sure if this makes much more sense as we still probably would want to load Hyde components from the current place. Closing for now. |
Reopening as I think we could actually load the Blade pages from the Edit: Yeah, this is what I'm looking for |
Since there are a few breaking changes that are going to happen here I will log them all here as they are made so I don't miss any later on when writing the changelog and upgrade guide. The config/view.php is updated to include the new source directory. Run php hyde publish:configs --force to update. |
This was actually much easier than I thought it would be. All tests are passing, docs just need to be updated. Drafting the PRs now. |
Laravel supports changing the source directories for Blade views. If Zero supports this properly and the publishable Hyde components also integrate it would make more sense to keep custom blade pages in a
_views
directory or similar.The text was updated successfully, but these errors were encountered: