lightning-flow-scanner-core - npm Package Compare versions

Comparing version 3.8.0 to 3.9.0

out/main/rules/AutoLayout.js

@@ -29,3 +29,3 @@ "use strict";
             name: 'AutoLayout',
-            label: 'Use Auto-Layout Mode',
+            label: 'Auto-Layout Mode',
             description: "With Canvas Mode set to Auto-Layout, Elements are spaced, connected, and aligned automatically, keeping your Flow neatly organized thus saving you time.",
@@ -32,0 +32,0 @@ supportedTypes: core.FlowType.allTypes(),

out/main/rules/ProcessBuilder.js

@@ -29,3 +29,3 @@ "use strict";
             name: 'ProcessBuilder',
-            label: 'Do not use Process Builder',
+            label: 'No Process Builder',
             description: "Salesforce is transitioning away from Workflow Rules and Process Builder in favor of Flow. Ensure you're prepared for this transition by migrating your organization's automation to Flow. Refer to official documentation for more information on the transition process and tools available.",
@@ -32,0 +32,0 @@ supportedTypes: core.FlowType.processBuilder,

out/main/store/DefaultRuleStore.js

@@ -14,2 +14,3 @@ "use strict";
 const MissingNullHandler_1 = require("../rules/MissingNullHandler");
+const ProcessBuilder_1 = require("../rules/ProcessBuilder");
 const SOQLQueryInLoop_1 = require("../rules/SOQLQueryInLoop");
@@ -29,2 +30,3 @@ const UnconnectedElement_1 = require("../rules/UnconnectedElement");
     MissingNullHandler: MissingNullHandler_1.MissingNullHandler,
+    ProcessBuilder: ProcessBuilder_1.ProcessBuilder,
     SOQLQueryInLoop: SOQLQueryInLoop_1.SOQLQueryInLoop,
@@ -31,0 +33,0 @@ UnconnectedElement: UnconnectedElement_1.UnconnectedElement,

package.json

 {
   "name": "lightning-flow-scanner-core",
-  "version": "3.8.0",
+  "version": "3.9.0",
   "main": "out/**",
@@ -5,0 +5,0 @@ "types": "index.d.ts",

readme.md

@@ -17,3 +17,3 @@ # Lightning Flow Scanner Core
 | **Auto Layout** ([`AutoLayout`](https://github.com/Lightning-Flow-Scanner/lightning-flow-scanner-core/tree/master/src/main/rules/AutoLayout.ts)) | With Canvas Mode set to Auto-Layout, Elements are spaced, connected, and aligned automatically, keeping your Flow neatly organized thus saving you time. |
-| **Outdated API Version* ([`APIVersion`](https://github.com/Lightning-Flow-Scanner/lightning-flow-scanner-core/tree/master/src/main/rules/APIVersion.ts)) | Introducing newer API components may lead to unexpected issues with older versions of Flows, as they might not align with the underlying mechanics. Starting from API version 50.0, the 'Api Version' attribute has been readily available on the Flow Object. To ensure smooth operation and reduce discrepancies between API versions, it is strongly advised to regularly update and maintain them. |
+| **Outdated API Version** ([`APIVersion`](https://github.com/Lightning-Flow-Scanner/lightning-flow-scanner-core/tree/master/src/main/rules/APIVersion.ts)) | Introducing newer API components may lead to unexpected issues with older versions of Flows, as they might not align with the underlying mechanics. Starting from API version 50.0, the 'Api Version' attribute has been readily available on the Flow Object. To ensure smooth operation and reduce discrepancies between API versions, it is strongly advised to regularly update and maintain them. |
 | **Copy API Name** ([`CopyAPIName`](https://github.com/Lightning-Flow-Scanner/lightning-flow-scanner-core/tree/master/src/main/rules/CopyAPIName.ts)) | Maintaining multiple elements with a similar name, like 'Copy_X_Of_Element,' can diminish the overall readability of your Flow. When copying and pasting these elements, it's crucial to remember to update the API name of the newly created copy. |
@@ -20,0 +20,0 @@ | **DML Statement In A Loop** ([`DMLStatementInLoop`](https://github.com/Lightning-Flow-Scanner/lightning-flow-scanner-core/tree/master/src/main/rules/DMLStatementInLoop.ts)) | To prevent exceeding Apex governor limits, it is advisable to consolidate all your database operations, including record creation, updates, or deletions, at the conclusion of the flow. |

src/main/rules/AutoLayout.ts

@@ -9,3 +9,3 @@ import * as core from '../internals/internals';
             name: 'AutoLayout',
-            label: 'Use Auto-Layout Mode',
+            label: 'Auto-Layout Mode',
             description: "With Canvas Mode set to Auto-Layout, Elements are spaced, connected, and aligned automatically, keeping your Flow neatly organized thus saving you time.",
@@ -12,0 +12,0 @@ supportedTypes: core.FlowType.allTypes(),

src/main/rules/ProcessBuilder.ts

@@ -9,3 +9,3 @@ import * as core from '../internals/internals';
             name: 'ProcessBuilder',
-            label: 'Do not use Process Builder',
+            label: 'No Process Builder',
             description: "Salesforce is transitioning away from Workflow Rules and Process Builder in favor of Flow. Ensure you're prepared for this transition by migrating your organization's automation to Flow. Refer to official documentation for more information on the transition process and tools available.",
@@ -12,0 +12,0 @@ supportedTypes: core.FlowType.processBuilder,

src/main/store/DefaultRuleStore.ts

@@ -11,2 +11,3 @@ import { APIVersion } from '../rules/APIVersion';
 import { MissingNullHandler } from '../rules/MissingNullHandler';
+import { ProcessBuilder } from '../rules/ProcessBuilder';
 import { SOQLQueryInLoop } from '../rules/SOQLQueryInLoop';
@@ -27,2 +28,3 @@ import { UnconnectedElement } from '../rules/UnconnectedElement';
   MissingNullHandler,
+  ProcessBuilder,
   SOQLQueryInLoop,
@@ -29,0 +31,0 @@ UnconnectedElement,

New alerts

License Policy Violation

License

This package is not allowed per your license policy. Review the package's license to ensure compliance.

Found 1 instance in 1 package

Fixed alerts

License Policy Violation

License

This package is not allowed per your license policy. Review the package's license to ensure compliance.

Found 1 instance in 1 package

Improved metrics

Total package byte prevSize

1069892

increased by0.02%

Lines of code

35252

increased by0.01%

No dependency changes