Evgeny

The last snippet is equivalent to: ```javascript { properties: { vehicles: { deepProperties: { "/driver/firstname" : {const: 'unknown'}, "1/damage" : // I assume it should not be relative in this...

I think it would require adding bigint support to ajv... It could potentially be limited just to this keyword, if you make the PR we can assess if it is...

> Why? well, because none of the keywords you expect to work with integer would work with bigint... Also, it seems to have a limited utility as JSON.parse cannot be...

You can use `verbose` option - it will include schema in the error. This keyword needs to be improved to report errors.

@Eomm thank you - I was thinking it is probably this issue. let me know if you need any advice on migrating to v8 in fastify v4.

I need to reproduce - looks like it’s a big, should be fixed

https://runkit.com/esp/58f244ff90f8c30014c36698

Maybe a keyword `{"prototypePropertyOf": "Object"}` similar to instanceOf that checks that the string is a prototype property of this class and then you can have `{ "not": {"prototypePropertyOf": "Object"}}`?

And if you want to filter out some property that fail some schema validation you could: `{"filterProperties": {...}}` where `...` could be `{ "not": {"prototypePropertyOf": "Object"}}`.

It won't work as propertyOf... the keyword value should be serialisable (e.g. a string), it can't be a reference to a prototype.