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
API Rename resources to _resources #8364
Conversation
To discuss:
|
@@ -55,8 +55,8 @@ protected function error($message = null) | |||
protected function installHeader() | |||
{ | |||
$clientPath = PUBLIC_DIR | |||
? 'resources/vendor/silverstripe/framework/src/Dev/Install/client' | |||
: 'resources/silverstripe/framework/src/Dev/Install/client'; | |||
? '_resources/vendor/silverstripe/framework/src/Dev/Install/client' |
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.
Why not use the constant for these bits?
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.
Laziness.
I don't see how this wouldn't be a breaking API change :( .
+1 for making this name configurable in 5.x. Can we do some composer.json configuration to make that work? |
I tend to agree with @ScopeyNZ. This will be very disruptive to our module ecosystem. Can we not do this but just make it configurable at the project level from SS5 on? |
Looks like we'll need to soft-code it. If it's not configured, it'll need to default to |
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.
As discussed, should be configurable, so we can allow devs to change the value in 4.x, and reconfigure to a safer default in 5.x.
#8364 should supersede this PR I think. Unless someone has objections, I'll close this one. |
Closing in favour of #8519 |
Fixes #7932
Requires silverstripe/vendor-plugin#25
Also all other modules will need to have their vendor-plugin dependency bumped to ^2 as well. My suggestion is to get the module merged first and migrate the modules one at a time.