You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I would like to propose an enhancement to the symfony/maker-bundle to allow the use of a custom Generator class in the Makers that implement the MakerInterface. This change would provide greater flexibility in creating classes in the desired namespaces and paths.
Currently, the MakerInterface defines the generate method as follows:
In this setup, the Generator class is tightly coupled with AutoloaderUtil, limiting customization options for generating files in specific namespaces and paths.
Proposed Change:
I suggest modifying the MakerInterface to accept a GeneratorInterface instead of a Generator. This would allow developers to implement their own Generator class that fits their specific needs.
I would like to propose an enhancement to the symfony/maker-bundle to allow the use of a custom Generator class in the Makers that implement the MakerInterface. This change would provide greater flexibility in creating classes in the desired namespaces and paths.
Currently, the MakerInterface defines the generate method as follows:
maker-bundle/src/MakerInterface.php
Line 52 in 9c85a83
In this setup, the Generator class is tightly coupled with AutoloaderUtil, limiting customization options for generating files in specific namespaces and paths.
Proposed Change:
I suggest modifying the MakerInterface to accept a GeneratorInterface instead of a Generator. This would allow developers to implement their own Generator class that fits their specific needs.
The new MakerInterface would look like this:
Benefits:
Implementation Considerations:
The text was updated successfully, but these errors were encountered: