Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR contains the following updates:
4.6.11
->5.3.0
Release Notes
ealush/vest (vest)
v5.3.0
Compare Source
v5.2.12
Compare Source
v5.2.11
Compare Source
v5.2.10
Compare Source
v5.2.9
Compare Source
v5.2.8
Compare Source
v5.2.7
Compare Source
v5.2.6
Compare Source
v5.2.5
Compare Source
v5.2.4
Compare Source
v5.2.3
Compare Source
v5.2.2
Compare Source
v5.2.1
Compare Source
v5.2.0
Compare Source
v5.1.5
Compare Source
v5.1.4
Compare Source
v5.1.3
Compare Source
v5.1.2
Compare Source
v5.1.1
Compare Source
v5.1.0
Compare Source
v5.0.5
Compare Source
v5.0.4
Compare Source
v5.0.3
Compare Source
v5.0.2
Compare Source
v5.0.1
: Vest@5.0.0Compare Source
Major version of Vest 5.0.0
Upgrading from V4 to V5
Migration guide
Vest 5 is mostly compatible with Vest 4, but some changes were made. In most cases, if you do not change anything, vest will keep working as it did before. However, to take advantage of the new features, you'll need to make some changes.
Eager execution mode is now the default
In previous versions of Vest, Vest continued validating fields even after one of their tests had failed. V5 changes that to improve the runtime performance, and instead, Vest will halt further validations of a given field if it failed. This was an opt-in feature, and it can now be removed.
To bring back the previous behavior, use the
mode
function that alters the execution mode:This also means that if you've used
skipWhen
to avoid running of failing fields, you can now remove it:All result methods are now available directly on the suite object
In previous versions, you had to call
suite.get()
to access the different methods, such asgetErrors
andisValid
. In V5, these methods are available directly on the suite object.Added
hasError
andhasWarning
methodsThe result object has two new methods: hasError and hasWarning. They return a boolean value indicating whether a given field has an error or a warning. With these new methods, you can display the first error of a field.
Removed skip.group and only.group
Vest 5 removes the dedicated group interface for skip and only, and instead allows you to call skip and only directly within the groups.
Optional fields now take into account the suite params
In previous versions, optional fields only took into consideration whether the tests ran or not. In V5 optional fields also search the data object passed to the suite. If it has an object with the optional field in it, and the optional field is blank - the test will be considered valid even if it is not passing.
Server side validations are built-in
In previous versions, as a user of Vest you had to set up your own state-reset mechanism. Vest now has a
staticSuite
export that does that for you.First-Class-Citizen typescript support
All of Vest's methods are now typed and make use of generics to enforce correct usage throughout your suite.
Dropped support for <ES2015
Vest 5 uses Javascript Proxies, which were introduced in ES2015. Therefore, Vest 5 no longer supports pre-ES2015 versions of Javascript. If you need to support older browsers, you can still use Vest 4.
v5.0.0
Compare Source
Configuration
📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.
🔕 Ignore: Close this PR and you won't be reminded about this update again.
This PR has been generated by Mend Renovate. View repository job log here.