-
Notifications
You must be signed in to change notification settings - Fork 92
Allow blueprints and field sets to be split repository #302
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
Allow blueprints and field sets to be split repository #302
Conversation
src/ServiceProvider.php
Outdated
| namespace Statamic\Eloquent; | ||
|
|
||
| use Illuminate\Foundation\Console\AboutCommand; | ||
| use JetBrains\PhpStorm\Deprecated; |
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.
This seems like a mistake. (You started using PhpStorm? 😄 )
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.
definitely a mistake.
i told you i'd give it a go... i don't hate it as much as i thought i would :)
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.
i think it added it when i added @deprecated in a comment
|
This is not push-back at all, but I'm just curious why someone would want blueprints in the db and fieldsets in files (and vice-versa). |
|
So the use case for TV2 is form blueprints only in the DB, other blueprints and fieldsets as file. |
|
Ah yeah I remember that conversation. Thanks. |
This PR allows blueprints and field sets to be run in split repository mode, ie the blueprints could be eloquent driven and field sets file driven, or vice versa.
It also fixes some of the code introduced in #300 to handle methods that were missed initially.