Closed queengooborg closed 2 years ago
Hey @queengooborg, I'm happy to accept contributions to support ajv-errors
. AFAIR, we don't mutate anything inside better-ajv-errors
.
I dug a little deeper into this, and I found that the original error data is moved into the params
object, so a fix should be pretty straightforward. I'll get a PR opened for this soon!
https://github.com/atlassian/better-ajv-errors/releases/tag/v1.2.0 has been released on npm
too. Thanks again for your contribution.
I am an owner of the MDN browser-compat-data project, and we use
ajv
withbetter-ajv-errors
. As indicated in https://github.com/mdn/browser-compat-data/issues/3256, we are wanting to useajv-errors
for custom errors to better represent the situation where a subfeature contains invalid characters (which is caught byadditionalProperties: false
). Doing a quick experiment, however, I found that it seems thatbetter-ajv-errors
doesn't get along withajv-errors
. It seems thatajv-errors
replaces the error type for some odd reason.It would be really wonderful to see support included so we can use both at the same time. Happy to spend time to do this one!