Errors extending schemas with yup >= 0.30 about json-schema-yup-transform

[leonbloy]

Additionally: if instead of using validate we use validateSync , the problematic statements also fail, differently:

    // the following does not throw error, but returns undefined 
    res = yupSchemaFull.validateSync({ text: 's', ab: { a: 'x', b: 'z' } });  
    // same: should throw exception, but returns undefined
    res = expect(() => yupSchemaFull.validateSync({ text: 's', ab: { a: 'x', b: 'too long' } })).toThrow(Error);

[leonbloy]

Update: it all works as expected if I revert yup to version "0.29.1"

Update2: it works until yup 0.29.3 , it breaks at yup 0.30.0
(the culprit -wild guess- might be jquense/yup@dcae108 )

[ritchieanesco]

@leonbloy v0.29.3 introduced breaking changes that are incompatible with this library.

[leonbloy]

@leonbloy v0.29.3 introduced breaking changes that are incompatible with this library.

(You probably meant v 0.30.0 - released in Nov 2020)
Well, then what? If this library is incompatible with the latest yup releases (that should documented prominently), are there plans to fix that?

[ritchieanesco]

Added the yup version this package supports in README here.
I may look to rewrite this library to be forward compatible, but that requires time and frankly, this was written for a work project in which I am no longer involved.

Feel free to raise a PR to make it compatible or fork the code and make changes to suit your needs.

[ritchieanesco]

@leonbloy 2.0.0-beta.0 has just been published that supports yup v0.32.11.

[leonbloy]

2.0.0-beta.0 has just been published that supports yup v0.32.11.

It's been 11 months since that beta. Meanwhile several fixes have been released to the main branch (which, it seems, were not merged to that beta branch). Also, a few days ago yup has released version 1.0. Are there any plans to merge and release a non beta version, compatible with yup latest version?