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
feature #59 Adding a new MakerInterface, instead of extending AbstractCommand (weaverryan)
This PR was squashed before being merged into the 1.0-dev branch (closes#59).
Discussion
----------
Adding a new MakerInterface, instead of extending AbstractCommand
Hi guys!
This diff looks big, but it makes no visible changes to the bundle. This only changes the way that custom maker commands are created: instead of extending from a base class and overriding methods, you'll implement the new `MakerInterface`. The reason behind this is simple: we need to tag a stable release and having a concrete interface gives us more flexibility going forward (i.e. we could add other optional interfaces for more functionality, deprecate this interface in favor of a new one, etc).
There are 2 powerful functional tests that pretty much cover everything. One actually tries all of the Maker classes to make sure they work (that existed before) and another tests that all Makers are wired correctly in the container.
The most important thing to look at is the new `MakerInterface`.
Cheers!
Commits
-------
8690210 adding public const explictly
34f8bbd adding phpcs rules and using short arrays
e3f5fa8 README tweak
22b7555 fabbot
0af6178 adding interface docs
c631196 updating README
1d22c8c Adding a new MakerInterface, instead of extending AbstractCommand
thrownewRuntimeCommandException(sprintf('The generator commands require your app to use Symfony Flex & a Flex directory structure. See https://symfony.com/doc/current/setup/flex.html'));
0 commit comments