Clarify 'composer update' message + generate *.php for Grav >= 1.7 #62
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.
I would like to suggest two changes:
From own experience and from post on forum, the message displayed after creating a 'new-plugin' is confusing when user is not familiar with composer. It is not clear that user must change directory into the folder of the new plugin. See also issue #61
When user creates plugin 'myplugin', new message would be:
Since Grav 1.7+ is now the default version people download, I would like to suggest the generated code is for Grav >= 1.7 and show comment when required version of Grav is < 1.7