-
Notifications
You must be signed in to change notification settings - Fork 26
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Upgrade Ajv dependency to v8 #58
Comments
Hi, Ajv v8 has been released on March 27. Do you plan to support it? I may help if needed. |
@jledentu Great question. I just checked the Breaking Changes between v7 and v8 and they seem fairly minor (https://github.com/ajv-validator/ajv/releases/tag/v8.0.0). I'm hoping to get the v2.2.0 release of this library out very soon and then I can focus on the v3.0.0 release. The original plan was for that release to introduce an upgrade from Ajv v6 to v7, but it looks like we might as well skip v7 and upgrade to v8. I'd love help with this, thank you! |
Thank you for working on this. In my use case, I was trying to use const { Validator } = require('express-json-validator-middleware');
const addFormats = require("ajv-formats");
const validator = new Validator();
addFormats(validator.ajv); but got errors like For anyone interested, the temporary workaround is to downgrade to |
I've published a beta release with Ajv v8. Please give it a try and let me know if you run into any issues!
This beta version should be compatible with the latest version of Ajv plugins such as ajv-formats. |
This library is currently using Ajv v6. Upgrading to Ajv v7 was proposed in pull request #55. In the meantime, Ajv v8 has been released, so we'll upgrade to that.
See: Changes from Ajv v6.12.6 to v8.0.0
TODO
Some of these may be worth breaking out into separate issues.
v8.8.2
)The text was updated successfully, but these errors were encountered: