Conversation
11233a8 to
81b6132
Compare
|
Any chance this could be merged sometime? I'd also like to see this feature, and it'd resolve #1135 |
There was a problem hiding this comment.
👎🏻 Making the template directory configurable means we have to maintain backward compatibility for filenames and the parameters passed to templates. This makes it much harder to make changes without breaking your usage. I am therefore opposed to this change.
|
Wouldn't it be better to simply... place the templates in the template directory, and have symfony resolve it like it does with twig? That way you wouldn't have to worry about backwards compatibility and anyone who'd like to override could simply do so using the built-in bundle override feature for templates |
Yes, this requires some procedures and avoids making random changes. Now, do the filenames change with each version? Isn't this a "Symfony" project, which is supposed to be a well-structured project? Your answer is surprising in this context. |
|
The ability to extend templates is requested by a large majority of users; perhaps they should be listened to. |
allow user to customize their templates by adding a config parameter to list templates folders.
generator will search in all folders listed in the configurations before to select its own template.
With that, user can modify one or more templates to get what he want without copy all maker classes :).
If no config is made => nothing move, all stay as before,
config can be set in a bundle (and the templates can be there too) to maximize reusability.
by example config can be :