v7.7.1

Bugfixes

• #2088 fix javascript error when running deploy by @JoernBerkefeld and @FiloMichal in #2095
• #2098 await file purging before building definitions by @JoernBerkefeld in #2099
• #2100 deleting transactional journeys now also locally deletes the associated transactionalEmail file locally. The API automatically deletes it on the server internally by @JoernBerkefeld in #2101

Chores

• #2102 add validation rule config setting 'fix' (next to already existing options 'off', 'warn', 'error') by @JoernBerkefeld in #2103
• #2090 enhanced eslint rules for mcdev projects by @JoernBerkefeld in #2091
• #2093 no longer auto-recognize vscode extension running mcdev to enable colors in test runs by @JoernBerkefeld in #2094
• #2096 auto-check config whenever it's loaded by @JoernBerkefeld in #2097

Full Changelog: v7.7.0...v7.7.1

Details

Advanced Configuration

Validation rules

You can define validation rules for retrieve, buildDefinition and deploy.

Possible rule settings are:

• not set, which implicitly turns off the rule
• "off" explicitly turns off the rule
• "warn" shows a log message of type warning
• "error" shows a log message of type error AND blocks further execution
  • for retrieve that prevents download
  • for buildDefintion (and build) that prevents the creation of the corresponding file in the deploy folder
  • for deploy this will prevent deployment.
• "fix" can either lead to skipping the component or to updating parts of the metadata (JSON) - that depends on the rule's algorithm. If fixing means skipping then the outcome is the same as with "error", except that no error code is returned by mcdev which can be relevant if you execute mcdev as part of a CI/CD pipeline where an error code signals a problem.