Carmine DiMascio

@pilerou [`validateRequests`](https://github.com/cdimascio/express-openapi-validator/wiki/Documentation#%EF%B8%8F-validaterequests-optional) takes the property `removeAdditional`. It seems reasonable for the values `all` and `true` to remove additional read-only props

Yes, PR is welcome. Note the AJV doc for removeAdditional https://ajv.js.org/options.html#removeadditional perhaps with express-openapi-valida, we add a new option readonly, that’s removes readonly additional fields

Closing as it is a Duplicate of the following https://github.com/cdimascio/express-openapi-validator/issues/104 Additionally, top level (not full discriminator) discriminator support exist exists https://github.com/cdimascio/express-openapi-validator/pull/461

Thanks a lot! I suspect this requires a bunch more work. It certainly requires tests. Contributions welcome :) I will plan to roll an alpha release, so folks can kick...

Will roll a new version soon

available in v.5.0.1

the new `useRequestUrl` option is available in v5.1.0. Set `useRequestUrl: true` in the validator options See PR https://github.com/cdimascio/express-openapi-validator/pull/857

This is interesting. If we can build it as a reusable module that both web apis i.e the existing middleware and sockets use, I'm all for it. Such an approach...

Thanks. This should be `peerDependencies`

@mawis this is interesting. could you create a PR with what you're thinking. best!