2.19.1

^0.30 restricts updates to only versions within the 0.30.x range, preventing upgrades to 0.32.0 for
bitexpert/phpstan-magento to allow upgrading within a major version notation ~0.30 is used.

Update yamllint configuration

Add option to add/edit whitelist or ignore patterns to yamllint.

2.18.0

What's Changed

• feat: execute Git hook within DDev by @youwe-petervanderwal in #26

New Contributors

• @youwe-petervanderwal made their first contribution in #26

Full Changelog: 2.17.1...2.18.0

2.17.1

What's Changed

• Added ignore_patterns support to allow project configurations to make use of this field through configuration overrides

Full Changelog: 2.17.0...2.17.1

2.17.0

What's Changed

• Feature/add bit expert phpstan by @rutgerrademaker in #22

Full Changelog: 2.16.2...2.17.0

Fix issue with 'alert' in blacklist

Changed

• alert( was removed from the git blacklist as it conflicts with PSR3. See #18

Resolve blacklist false-positives for specific function names

2.16.1

Changed

• Git blacklist now matches on words instead of characters by default.
• The git blacklist configuration for rejecting accidentally commited merge conflicts now properly reflects the
  full set of characters used by git.

Fixed

• Resolved issue where the updated git blacklist configuration would provide a false positive result
  on functions ending with add() or odd() due to checks on dump and die dd() statements.

Added

• Git blacklist now checks for exit() usage.

Fix installation breaking for pimcore-project types

2.16.0

Fixed

• Testing suite no longer breaks during installation when composer project type is set to pimcore-project.

Added

• phpcs.xml, phpmd.xml and phpstan.neon files are now automatically installed in a local pimcore-project if they don't exist yet.

Split out grumphp configuration into magento2 and pimcore options

2.15.0

Added

• Project type resolver can now look for pimcore projects.
  • Pimcore projects have their own git blacklist configuration.
  • In the future, the pimcore coding standard will have its own package for phpcs.xml and phpmd.xml rulesets.
• grumphp.yml file for pimcore projects.
  • This file falls back on the default configuration and inherits all properties, except for the blacklist triggers.
• Git blacklist documentation.

Changed

• The magento2 grumphp.yml file is split off from the default configuration.
  • The grumphp.yml that's part of a project will automatically point to the new magento2-specific config file.
  • The new file falls back on the default configuration, and overrides the git blacklist keywords and triggers.
  • The magento specific constructs are also removed from the default grumphp.yml template.
• The default phpcs.xml file now references a relative ruleset instead of an absolute path.

Add new coding standards of magento 2

Added
New pathing for phpcs.xml file.

• This release adds magento coding standards to phpcs code style. see https://github.com/magento/magento-coding-standard.
  Support for phtml in project type Magento2. The phtml files will only be checked based on Magento2 code standards.
  Changed
• Project type default/magento use correct index replaced excludes_analyse with excludePaths for phpstan.neon file.
• Project type default use correct tags for phpunit_dist.xml.
• Updated dependency to youwe/composer-dependency-installer
  Changed
• Phpcs will now also check files phtml. If not preferred behaviour overwrite parameter phpcs.triggered_by in grumphp.yml and change back to [php].
• .eslintrc.json which was updated coherent to Fisheye configurations.