Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Remove plugin namespace aliasing and shortening.
Aliasing a plugin namespace in app won't work as the plugin itself could be using plugin notation with hardcoded name.
- Loading branch information
Showing
2 changed files
with
6 additions
and
50 deletions.
There are no files selected for viewing
This file contains 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
This file contains 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
9aca863
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.
Before this change, I could have a company plugin under a company namespace (i.e. Acme\MyPlugin) and load it using:
Now, I can't load it anymore. Looking at the tests, looks like I would need the plugin to reside under the 'plugin/Acme/MyPlugin'. Right now, using 'cakephp-plugin' in composer.json, it gets automatically installed to 'plugin/MyPlugin'.
What's the best way to get this to work again?
9aca863
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.
Specify
installer-name
similar to this.9aca863
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.
Thanks. Just to make sure, no other way than by updating the plugins? I was trying not to have to do that ;)
9aca863
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.
At the moment if you are using vendor namespace only option is to update your
composer.json
. We are looking into ways to possibly avoid that.9aca863
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.
Ok, thanks.