Releases: craftcms/generator
Releases · craftcms/generator
2.1.0
1.8.0
- Generated plugins and modules now call
$this->attachEventHandlers()
directly frominit()
, and clarify whenonInit()
should be used.
2.0.1
2.0.0
- Craft Generator now requires Craft 5.
- Renamed
craft\generator\Command\EVENT_REGISTER_GENERATOR_TYPES
toEVENT_REGISTER_GENERATORS
.
1.7.0
1.6.1
- Fixed a double-backslash bug.
1.6.0
- Added
craft\generator\BaseGenerator::messageTwig()
. (#25) - The plugin generator now ensures that the project’s
composer.json
file hasminimum-stability: dev
andprefer-stable: true
set. (#22) - Fixed a bug where the Service generator was suggesting adding a
config()
method which defined the service config, even when the target was a module. (#24)
1.5.0
- Improved the validation error for private plugins’ handle prompts, for handles that don’t begin with an underscore. (#18)
- The plugin generator’s “Minimum Craft CMS version” prompt now defaults to the initial minor release of the current Craft version (e.g.
4.4.0
rather than4.4.11
), if running a stable release of Craft 4.4 or later. - The plugin generator now warns against using non-unique plugin handles.
- Generated plugins’ and modules’
init()
methods now have avoid
return type. (#20) - Fixed a bug where it was possible to enter invalid UTF-8 characters into the plugin generator prompts, causing an exception when writing the
composer.json
file. - Craft CMS 4.4.11+ is now required.
1.4.0
- Generated plugins now include a “Create Release” GitHub action, which will create a new GitHub Release whenever the Craft Plugin Store is notified of a new version tag.
- Fixed a PHP error that occurred when generating a private plugin, if a different minimum Craft version was entered.