Releases: Lightning-Flow-Scanner/lightning-flow-scanner-core
4.8.0 | Community Release
What's Changed
New & Changed Rules:
| Rule (Configuration ID) | Description |
|---|---|
Same Record Field Updates (SameRecordFieldUpdates) |
Much like triggers, before contexts can update the same record by accessing the trigger variables $Record without needing to invoke a DML. |
Missing Fault Path (MissingFaultPath) |
At times, a flow may fail to execute a configured operation as intended. By default, the flow displays an error message to the user and notifies the admin who created the flow via email. However, you can customize this behavior by incorporating a Fault Path. |
Trigger Order (TriggerOrder) |
Guarantee your flow execution order with the Trigger Order property introduced in Spring '22 |
- chore: add tests for exceptions by @junners in #133
- add tests for core.fix by @k-capehart in #135
- fix(RuleEngine): missing fault path rule modification resolved #134 by @junners in #139
- feat(RuleEngine): same record field update new rule fixes #134 by @junners in #140
- feat(RuleEngine): make rule imports for non default rule store rules by @junners in #141
- tests(RuleEngine): add unit tests for same record field updates by @junners in #142
- feat(RuleEngine): trigger order on record triggered flows by @junners in #143
Full Changelog: v4.5.0...v4.8.0
Contributors
Assets 2
4.7.0 | Community Release
What's Changed
New & Changed Rules:
| Rule (Configuration ID) | Description |
|---|---|
Same Record Field Updates (SameRecordFieldUpdates) |
Much like triggers, before contexts can update the same record by accessing the trigger variables $Record without needing to invoke a DML. |
Missing Fault Path (MissingFaultPath) |
At times, a flow may fail to execute a configured operation as intended. By default, the flow displays an error message to the user and notifies the admin who created the flow via email. However, you can customize this behavior by incorporating a Fault Path. |
- chore: add tests for exceptions by @junners in #133
- add tests for core.fix by @k-capehart in #135
- fix(RuleEngine): missing fault path rule modification resolved #134 by @junners in #139
- feat(RuleEngine): same record field update new rule fixes #134 by @junners in #140
Full Changelog: v4.5.0...v4.6.0
Contributors
Assets 2
4.6.0 | Community Release
What's Changed
New & Changed Rules:
| Rule (Configuration ID) | Description |
|---|---|
Same Record Field Updates (SameRecordFieldUpdates) |
Much like triggers, before contexts can update the same record by accessing the trigger variables $Record without needing to invoke a DML. |
Missing Fault Path (MissingFaultPath) |
At times, a flow may fail to execute a configured operation as intended. By default, the flow displays an error message to the user and notifies the admin who created the flow via email. However, you can customize this behavior by incorporating a Fault Path. |
- chore: add tests for exceptions by @junners in #133
- add tests for core.fix by @k-capehart in #135
- fix(RuleEngine): missing fault path rule modification resolved #134 by @junners in #139
- feat(RuleEngine): same record field update new rule fixes #134 by @junners in #140
Full Changelog: v4.5.0...v4.6.0
Contributors
Assets 2
4.5.0 | Community Release
What's Changed
- chore: bump npm deps to resolve cve by @junners in #131
- chore: remove eol node 18 by @junners in #132
Full Changelog: v4.3.0...v4.5.0
Contributors
Assets 2
4.4.0 | Community Release
What's Changed
Full Changelog: v4.3.0...v4.4.0
Contributors
Assets 2
4.3.0 | Community Release
Contributors
Assets 2
4.2.0 | Community Release
What's Changed
Full Changelog: v4.1.0...v4.2.0
Contributors
Assets 2
4.1.0 | Community Release
What's Changed
Breaking Change
We've doubled down on developer experience and made our app even easier to integrate! Engineers can now just import('lightning-flow-scanner-core') as a dependency, no more importing of out directory!
End users can now enjoy a snappier response from all the apps as the overall package size is reduced from ~1.4MB to ~400 KB that's a whole megabyte gone!
Tests are also now up-to-date with industry standards and runs on Mocha 10, Chai 5, Ts-node latest on a commonjs project!
Releases can now be done with 2 clicks from Github Actions
- feat: migrate to mocha 5 by @junners in #115
- Feature/v4.0.0 by @junners in #116
- chore: add push tag as an example by @junners in #117
Full Changelog: v3.22.0...v4.1.0
Contributors
Assets 2
4.0.0 | Community Release
What's Changed
Breaking Change
We've doubled down on developer experience and made our app even easier to integrate! Engineers can now just import('lightning-flow-scanner-core') as a dependency, no more importing of out directory!
End users can now enjoy a snappier response from all the apps as the overall package size is reduced from ~1.4MB to ~400 KB that's a whole megabyte gone!
Tests are also now up-to-date with industry standards and runs on Mocha 10, Chai 5, Ts-node latest on a commonjs project!
- feat: migrate to mocha 5 by @junners in #115
- Feature/v4.0.0 by @junners in #116
- chore: add push tag as an example by @junners in #117
Full Changelog: v3.22.0...v4.0.0
Contributors
Assets 2
3.22.0 | Community Release
What's Changed
Housekeeping release and keep our application up-to-date with the current industry standards!
- fix(deps): bump uglify-js from 3.19.0 to 3.19.1 by @dependabot in #111
- fix(deps): bump husky from 9.1.1 to 9.1.4 by @dependabot in #113
- fix(deps): bump typescript-eslint from 7.17.0 to 8.0.0 by @dependabot in #112
- fix(deps): bump eslint from 8.57.0 to 9.8.0 by @dependabot in #114
Full Changelog: v3.21.0...v3.22.0
