Bump jsonpath-plus and json-rules-engine in /examples

[dependabot]

Bumps jsonpath-plus to 10.1.0 and updates ancestor dependency json-rules-engine. These dependencies need to be updated together.

Updates jsonpath-plus from 4.0.0 to 10.1.0

Release notes

Sourced from jsonpath-plus's releases.

v7.2.0

7.2.0 (2022-09-02)

• perf: optimize walk method by 10%-34% (@​jacobroschen)
• chore: add types to exports field (@​awlayton)

v6.0.1

6.0.1 (2021-07-07)

• Fix: Some package.json paths needed updating (@​matushorvath)
• npm: Update devDeps.

v6.0.0

6.0.0 (2021-07-05)

User-impacting

• Breaking enhancement: Create as true ESM module
• Breaking change: Utilize .cjs extension for UMD and CJS builds (very old browsers might not support, but needed with the change given that Webpack may complain if there even exists CJS within what it thinks is an ESM file, the ".js", our default)
• Breaking change: Utilize .js extension instead of .mjs for now default ESM builds

Dev-impacting

• npm: Add lint script
• npm: Update devDeps.

v5.1.0

5.1.0 (2021-06-24)

• Enhancement: support double-quoted bracket notation
• Linting: As per latest ash-nazg
• npm: Update devDeps.

v5.0.7

5.0.7 (2021-04-12)

• Fix: Add packge.json to exports (@​sebastiendavid)

v5.0.6

5.0.6 (2021-04-09)

• Fix: Remove static modifiers (@​sdolski)
• Linting: As per latest ash-nazg
• npm: Update devDeps.

v5.0.5

5.0.5 (2021-04-09)

... (truncated)

Changelog

Sourced from jsonpath-plus's changelog.

10.1.0

• feat: add typeof operator to safe script

10.0.7

• fix(security): prevent constructor access
• docs: add security policy file

10.0.6

• fix(security): prevent call/apply invocation of Function

10.0.5

• fix: remove overly aggressive disabling of native functions but disallow __proto__

10.0.4

• fix(security): further prevent binding of Function calls which may evade detection

10.0.3

• fix(security): prevent binding of Function calls which may evade detection

10.0.2

• fix(security): prevent Function calls outside of member expressions

10.0.1

• fix(security): prohibit Function in "safe" vm

10.0.0

BREAKING CHANGES:

• Require Node 18+

• fix(security): use safe vm by default in Node

• chore: bump jsep, devDeps. and lint

9.0.0

BREAKING CHANGES:

• Removes preventEval property. Prefer eval: false instead.

• Changed behavior of eval property. In the browser, eval/Function won't be used by default to evaluate expressions. Instead, we'll safely evaluate using a subset of JavaScript. To resume using unsafe eval in the browser, pass in the option eval: "native"

• feat: add safe eval for browser and eval option (#185) (@​80avin)

• feat: add ignoreEvalErrors property (@​80avin)

... (truncated)

Commits

• 93612a3 chore: bump version
• 4a16cbd feat: add undefined, null literals to safe script
• f119fe3 feat: add typeof operator to safe script
• b70aa71 fix(security): prevent constructor access in safe vm
• 763ada0 fix(security): prevent call/apply invocation of Function
• 98a6b22 fix: remove overly aggressive disabling of native functions but disallow `__p...
• 30194c7 fix(security): further prevent binding of Function calls which may evade dete...
• eac48fe fix(security): prevent binding of Function calls which may evade detection
• 34a836b chore: bump version
• 5a22e3f fix(security): prevent Function calls outside of member expressions
• Additional commits viewable in compare view

Updates json-rules-engine from 6.0.0-alpha-3 to 7.0.0

Release notes

Sourced from json-rules-engine's releases.

v6.5.0

What's Changed

• Custom almanac by @​chris-pardy in CacheControl/json-rules-engine#357

A custom Almanac implementation can now be passed to the Engine.run method. This Almanac will be used in place of the default one. This allows for extensions to looking up Fact Values, or other caching behavior.

Support Facts in Events

Events can now include references to facts in their parameters. If the replaceFactsInEventParams flag is set to true on the engine options then the references to fact values will be replaced with the resolved values when the facts are emitted.

6.3.0

Release Notes

• Added support for named conditions that can be shared between rules
  • Documentation: https://github.com/CacheControl/json-rules-engine/blob/master/docs/engine.md#enginesetconditionstring-name-object-conditions
  • PR: CacheControl/json-rules-engine#339

6.2.0

Release Notes

• Thanks to @​andycoopcode the new not condition makes it easier to write complex conditions by allowing top-level negation rather than requiring factoring of a nested condition:
  • Documentation: https://github.com/CacheControl/json-rules-engine/blob/master/docs/rules.md#boolean-expressions-all-any-and-not
  • PR: CacheControl/json-rules-engine#275
  • Issue: CacheControl/json-rules-engine#269
• Thanks to @​chris-pardy you can now add a name field on conditions to make them more human readable.
  • PR: CacheControl/json-rules-engine#332
  • Issue: Optional Condition Naming CacheControl/json-rules-engine#331

Dependencies

• jsonpath-plus has been upgraded from ^5.0.7 -> ^7.0.0
• hash-it has been upgraded from ^5.0.0 -> ^6.0.0

Doc Fixes

• Thanks to @​rbrtmrtn there have been some style fixes to the almanac.md document
  • PR: CacheControl/json-rules-engine#283

Changelog

Sourced from json-rules-engine's changelog.

6.1.0 / 2021-06-03

• engine.removeRule() now supports removing rules by name
• Added engine.updateRule(rule)

6.0.1 / 2021-03-09

• Updates Typescript types to include failureEvents in EngineResult.

6.0.0 / 2020-12-22

• BREAKING CHANGES
  • To continue using selectn syntax for condition paths, use the new pathResolver feature. Read more here. Add the following to the engine constructor:

    const pathResolver = (object, path) => {
      return selectn(path)(object)
    }
    const engine = new Engine(rules, { pathResolver })

    (fixes #205)
  • Engine and Rule events on('success'), on('failure'), and Rule callbacks onSuccess and onFailure now honor returned promises; any event handler that returns a promise will be waited upon to resolve before engine execution continues. (fixes #235)
  • Private rule.event property renamed. Use rule.getEvent() to avoid breaking changes in the future.
  • The success-events fact used to store successful events has been converted to an internal data structure and will no longer appear in the almanac's facts. (fixes #187)
• NEW FEATURES
  • Engine constructor now accepts a pathResolver option for resolving condition path properties. Read more here. (fixes #210)
  • Engine.run() now returns three additional data structures:
    • failureEvents, an array of all failed rules events. (fixes #192)
    • results, an array of RuleResults for each successful rule (fixes #216)
    • failureResults, an array of RuleResults for each failed rule

5.3.0 / 2020-12-02

• Allow facts to have a value of undefined

5.2.0 / 2020-11-31

• No changes; published to correct an accidental publish of untagged alpha

5.0.4 / 2020-09-26

• Upgrade dependencies to latest

5.0.3 / 2020-01-26

• Upgrade jsonpath-plus dependency, to fix inconsistent scalar results (#175)

5.0.2 / 2020-01-18

• BUGFIX: Add missing DEBUG log for almanac.addRuntimeFact()

5.0.1 / 2020-01-18

• BUGFIX: DEBUG envs works with cookies disables

5.0.0 / 2019-11-29

• BREAKING CHANGES
  • Rule conditions' path property is now interpreted using json-path
    • To continue using the old syntax (provided via selectn), npm install selectn as a direct dependency, and json-rules-engine will continue to interpret legacy paths this way.

... (truncated)

Commits

• See full diff in compare view

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

---

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

• @dependabot rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot merge will merge this PR after your CI passes on it
• @dependabot squash and merge will squash and merge this PR after your CI passes on it
• @dependabot cancel merge will cancel a previously requested merge and block automerging
• @dependabot reopen will reopen this PR if it is closed
• @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
• @dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
• @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)
  You can disable automated security fix PRs for this repo from the Security Alerts page.