Releases: Flow-Scanner/lightning-flow-scanner-cli
3.11.0 | Community Release
Contributors
Assets 2
3.9.0 | Community Release
What's Changed
New Rule!
| Rule (Configuration ID) | Description |
|---|---|
Hardcoded Url (HardcodedUrl) | Avoid hard-coding URLs as they are org-specific. Instead, use a $API formula (preferred) or you can use an environment-specific such as custom labels, custom metadata, or custom settings. |
Full Changelog: v3.8.0...v3.9.0
Contributors
Assets 2
3.8.0 | Community Release
What's Changed
New Rule in beta!
| Rule (Configuration ID) | Description |
|---|---|
Get Record All Fields (GetRecordAllFields) | Following the principle of least privilege (PoLP), avoid using Get Records with 'Automatically store all fields' unless necessary. |
Full Changelog: v3.7.0...v3.8.0
Contributors
Assets 2
3.7.0 | Community Release
Full Changelog: v3.6.0...v3.7.0
3.6.0 | TrueNorthDreamin' Special Releae
What's Changed
Full Changelog: v3.5.0...v3.6.0
Contributors
Assets 2
3.4.0 | Community Release
New Rule
This rule is opt-in only while running in beta
to opt-in, use modify your .flow-scanner.yml configuration with the ff:
rules: RecursiveAfterUpdate: severity: error| Rule (Configuration ID) | Description |
|---|---|
Recursive After Update (RecursiveAfterUpdate) | After updates are meant to be used for record modifications that are not the same record that triggered the flow. Using after updates on the same record can lead to recursion and unexpected behavior. Consider using before save flows for same record updates. |
What's Changed
Full Changelog: v3.3.0...v3.4.0
Contributors
Assets 2
3.3.0 | Community Release
CVE and Security Fixes
Full Changelog: v3.2.1...v3.3.0
3.2.0 | Community Release
What's Changed
Rule Activation!
| Rule (Configuration ID) | Description |
|---|---|
Trigger Order (TriggerOrder) | Guarantee your flow execution order with the Trigger Order property introduced in Spring '22 |
Full Changelog: v3.1.0...v3.2.0
Contributors
Assets 2
3.1.0 | Community Release
What's Changed
Full Changelog: v3.0.0...v3.1.0
Contributors
Assets 2
3.0.0 | Community Release
New Rule
Cyclomatic Complexity developed by Thomas McCabe Sr, is one of the gold standard for measuring how complex your code is, at it's core, it's counting how many independent paths can your code take. This simple metric has existed on tools such as PMD which can be used on Java & Apex, and as of today, also Flows.
| Rule | Description |
|---|---|
Cyclomatic Complexity (CyclomaticComplexity) | The number of loops and decision rules, plus the number of decisions. Use a combination of 1) subflows and 2) breaking flows into multiple concise trigger ordered flows, to reduce the cyclomatic complexity within a single flow, ensuring maintainability and simplicity. |
Breaking Change
Full Changelog: v2.46.0...v3.0.0