Skip to content

Releases: regevbr/json-expression-eval

v7.1.0

12 Nov 12:50
7c62ee9
Compare
Choose a tag to compare

Added

Added support for node 20 #35

v7.0.2

30 Mar 18:03
e35e182
Compare
Choose a tag to compare

updated license to MIT

v7.0.1

27 Feb 23:08
eacfe7d
Compare
Choose a tag to compare

Fixed

Fixed default values for genercis

v7.0.0

27 Feb 22:23
e1c27ec
Compare
Choose a tag to compare

Added

Added ability to pass custom run options to custom functions/rules. This can be handy, for example, if you want to perform a dry run without making any external API calls, but using the current context (and not the validation one)

BREAKING CHANGES

  • Dropped support for node < 14
  • Some default generics values are now required - please see README for examples
  • All function calls now require passing the new custom run options

v6.0.0

04 Dec 15:11
b3e6e1a
Compare
Choose a tag to compare

BREAKING CHANGE

Currently, during validation, we don't run the expression functions, not allowing them to be validated.
This major version always runs the expression functions and custom rules, while passing a new third argument stating that validation occurs, to allow the functions to only perform validation and skip business logic.

v5.1.2

13 Oct 14:48
49a26b8
Compare
Choose a tag to compare

Add support for node 18

v5.1.1

06 Sep 15:05
9515b9b
Compare
Choose a tag to compare

fixed issue that can cause typescript error on deep type initialization

v5.1.0

30 Aug 19:07
559bd68
Compare
Choose a tag to compare

added ability to perform math operations on context properties

v5.0.0

29 Aug 12:29
476edef
Compare
Choose a tag to compare

BREAKING CHANGES

  • the api now is completely async, allowing custom rules and user-defined functions to be async in nature.

v4.3.0

29 Aug 11:33
5ad068e
Compare
Choose a tag to compare
  • Added ability to reference the context on the right-hand side of the expressions