Add networknt json-schema-validator to the Java validator list #302
Conversation
|
Deploy preview for condescending-hopper-c3ed30 ready! Built with commit e4fd78f https://deploy-preview-302--condescending-hopper-c3ed30.netlify.com |
|
I'm not part of this project, but I think your project already exists in the obsolete list, so you might want to remove it there. |
|
I'm confused- #303 looked like it fixed both files but was closed? |
Sorry, I created that pull request before I realized this one existed, and this one is from the original author of the library. So I closed mine. |
|
OK yeah, agree this should also be removed from implementations-obsolete.md |
|
If the OP doesn't fix it we'll edit it further and merge it eventually |
|
@slisaasquatch @handrews Thanks for pointing out the obsolete list. I have removed it from the list already. |
|
Thanks Steve! Merged! As an aside, taking a quick look, I couldn't tell if you used the official test suite or not. |
|
@Relequestual You are right. The library is used in the light-4j framework to validate the request/response during runtime. It has a configuration to switch between pure JSON schema validation and OpenAPI 3.0 schema validation as there are some differences. I will sync with the latest official test cases again. Thanks a lot for the reminder. |
|
@stevehu Super! At least you recognise there are differences and they matter! |
|
@stevehu fortunately in the future, OpenAPI 3.1 will use a fully compatible superset of JSON Schema draft 2019-09 (formerly known as draft-08), and present the extensions as a recognizable JSON Schema vocabulary, so eventually such special-casing won't be needed anymore. |
|
@handrews That is what I have heard. I am so glad two teams are working together :) |
No description provided.