Releases: Flow-Scanner/lightning-flow-scanner-core
Releases · Flow-Scanner/lightning-flow-scanner-core
v4.42.0
4.41.0
4.40.0 | Community Release
What's Changed
Full Changelog: v4.39.0...v4.40.0
4.39.0 | Community Release
Full Changelog: v4.38.0...v4.39.0
4.38.0 | Community Release
What's Changed
- fix(#227): custom errors element parsing by @junners in #229 contributed by @Mjohnson047
Full Changelog: v4.37.0...v4.38.0
4.37.0 | Community Release
What's Changed
Full Changelog: v4.36.0...v4.37.0
4.36.0 | Community Release
New Rule
Rule (Configuration ID) | Description |
---|---|
Action Calls In Loop (ActionCallsInLoop ) |
To prevent exceeding Apex governor limits, it is advisable to consolidate and bulkify your apex calls, utilize a single action call containing a collection variable at the end of the loop. |
What's Changed
- feat(#216): action calls in loop initial onboarding by @junners in #224
- closes (#216) rule submission by @tomkittlabs
Full Changelog: v4.35.0...v4.36.0
4.35.0 | Community Release
What's Changed
Full Changelog: v4.34.0...v4.35.0
4.34.0 | Community Release
What's Changed
- fix: transform elements to be parsed as flow nodes #220 by @junners in #221
- fix issue #220 from @RaviVaranasi
Full Changelog: v4.33.0...v4.34.0
4.33.0 | Community Release
What's Changed
Beta Rules now has it's own store, this means that consumers can now know what rules are in beta.
This enables vsce extension to be aware of the beta rules and offer them up
Full Changelog: v4.32.0...v4.33.0