Display Severity and Issues per Severity Level

Thanks to @nvuillam's contribution, we bring to you:

• Severity in flow errors details
• Summary of number of issues by severity

Upgrade Core to 2.28

Handles an issue with the handling of Flows that have multiple loops

Upgrade Core to 2.27

This brings some small improvements:

• Bugfix for supporting scheduled flows in our compiler by @junners
• Improves error handling for incorrect rule configurations

Upgrade Core to 2.26

1. DMLStatementInLoop Rule:

   • The rule has undergone refinement to enhance accuracy in identifying DML statements within loops.
   • The traversal logic has been improved to account for nested loops, ensuring precise detection of DML statements within these structures.
   • To enhance maintainability, the rule has been split into a separate class.

2. SOQLQueryInLoop Rule:

   • Introducing a new rule, SOQLQueryInLoop, which identifies instances of SOQL queries executed inside loops. This addition promotes best practices and aids in optimizing code for governor limits.

3. Flow Compiler Class:

   • A new class, the Flow Compiler, has been introduced to elevate the capabilities of our rule-checking process. This addition allows for more sophisticated and uniform analyses of Salesforce flows.

https://github.com/Lightning-Flow-Scanner/lightning-flow-scanner-core/releases/tag/2.26

Fix wrong exitCode

What's Changed

• Fix wrong exitCode when errors are found by @nvuillam in #72

Full Changelog: 2.11...v2.12.0

Fix False positives 'FlowDescription' & 'MissingDescription' rules

Fixes the following bugs:

• False positive 'FlowDescription' rule
• False positive 'MissingNullHandler' rule

2.9 Bugfix folder scan & human output

some bugs have been fixed in 2.9 regarding including node modules in the scope of the scan and also the issues in the human output

New Rule: Copy of API Name

New Rule: Copy of API Name

Having multiple elements called Copy_X_Of_Element will decrease the readability of the Flow. If you copy and paste them, make sure to update the API name of the new copy.

Configuration ID: CopyOf (View source code)

Old API Versions & Flow Naming Conventions

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)

---

lightning-flow-scanner v2.3.0

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.