You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
@nkgm So is the intended effect here to ensure all validators, async or not have resolved before determining the changesets validation is done? This seems reasonable...
This is derived from a relevant
tests/unit/changeset-test.js
test:The above assertion fails because
async
's validation still hasn't resolved by the timevalidate()
is called. Is this intended behavior?If the changeset is created with
{ skipValidate: true }
the assertion passes.The text was updated successfully, but these errors were encountered: