Introducing two new configurable rules!

1. Old API Version
2. Flow Naming Convention

1. Old API version

Newer API components may cause older versions of Flows to start behaving incorrectly due to differences in the underlying mechanics. The Api Version has been available as an attribute on the Flow since API v50.0 and it is recommended to limit variation and to update them on a regular basis.

Default Value: >50.0

Configuration example:

APIVersion: { severity: 'error', expression: '===58' } 

Configuration ID: APIVersion (View source code)

2. Flow naming conventions

Readability of flow is very important. Agreeing on and following the same naming conventions will ease collaboration.

Default Value: [A-Za-z0-9]+_[A-Za-z0-9]+

Configuration example:

FlowName: { severity: 'error', expression: '[A-Za-z0-9]' } 

Configuration ID: FlowName (View source code)

DuplicateDMLOperations now also returns false when the navigation of the screen after a DML has been hidden completely and not just the previous navigational button.

What's Changed

• BREAKING CHANGE: --throwerrors argument is not available anymore and is replaced by --failon, that has more options
  • New argument --failon (error/warning/note): Makes return code 1 in case --failon severity is reached
• Use cosmiconfig to load configuration, allowing JSON & YAML
• Provide human-readable output format
  • Sort errors by flow
  • Display issue severity
• Update documentation in README
  • Human format output screenshot
  • Shields.io badges
  • Describe rules
• Upgrade lightning-flow-scanner-core dependency to 2.5.0
• Fix npm package generation (please do not use v2.0.0 ,but use v2.1.0)

Contributors

• @RubenHalman
• @nvuillam