Add ability to configure config, controllers, models, views directories generated in the module#1549
Open
elcreator wants to merge 1 commit intophalcon:5.0.xfrom
Open
Add ability to configure config, controllers, models, views directories generated in the module#1549elcreator wants to merge 1 commit intophalcon:5.0.xfrom
elcreator wants to merge 1 commit intophalcon:5.0.xfrom
Conversation
…es generated in the module
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Hello!
In raising this pull request, I confirm the following (please check boxes):
Small description of change:
Phalcon is flexible so code generator should be too - i.e. I want PSR compatible Controllers, Views, Models instead of controllers, view, models and someone my name them i.e. Ctrl, View, Model.
Also optional routes addition file may be beneficial (if user place desired Routes.php in their templates dir).
I.e. I prefer to see all routes related to the feature (module) and who is intended to use them in one place rather than disseminated in docblocks.
Thanks