Skip to content

Releases: regevbr/json-expression-eval

v8.2.1

18 Dec 09:05
5efe82a

Choose a tag to compare

Add tests (#47)

v8.2.0

17 Dec 14:38
80eafdb

Choose a tag to compare

feat: npm auth (#46)

v8.1.0

07 Nov 10:24
dcc6dd3

Choose a tag to compare

What's Changed

Full Changelog: v8.0.1...v8.1.0

v8.0.1

05 Nov 12:17
6366ef0

Choose a tag to compare

What's Changed

Full Changelog: v8.0.0...v8.0.1

v8.0.0

05 Nov 11:55
b2efd94

Choose a tag to compare

drop support for node 14 and 16 and add support for node 22 and 24

What's Changed

Full Changelog: v7.1.0...v8.0.0

v7.1.0

12 Nov 12:50
7c62ee9

Choose a tag to compare

Added

Added support for node 20 #35

v7.0.2

30 Mar 18:03
e35e182

Choose a tag to compare

updated license to MIT

v7.0.1

27 Feb 23:08
eacfe7d

Choose a tag to compare

Fixed

Fixed default values for genercis

v7.0.0

27 Feb 22:23
e1c27ec

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

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.