Moving plugin files into a single contained folder for ease of use. #11
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.
Many popular Craft plugins keep all core plugin files within a folder of the desired plugin name. This makes it very easy to identify the files which are core to the plugin itself. In build processes that I use, the github tarball is extracted to a vendor folder and then the core folder is symlinked to the craft plugin directory. Reminiscent of how composer would handle things.
I won't take any offence if you reject this... just thought I would propose it!