Update "Validating OpenAPI and JSON Schema" post #704
Conversation
There was a problem hiding this comment.
Nice job with this article! I learned a lot while reading it. I think there is range for more posts in this intersection between OpenAPI and JSON Schema.
Looks great to me. My only thought regarding the format of the article: The article ends after the last sub-section of the "Supporting multiple dialects" with a cold end for what was a great article. My suggestion is adding a closing paragraph or closing thoughts section to avoid that cold end.
|
Do we want to change the spirit of the article? I think this change is just updating for relevant code samples. |
It is all right from my side. I approved the PR but also shared my opinion just in case it resonates to Jason. |
|
@benjagm is absolutely right that this post would be better if it had a proper conclusion. I remember writing it and couldn't think of a way to end it. I don't have a problem with updating an old post, but I'm a bit overloaded at the moment and don't want to delay releasing this update until I have time to come back to this and work on adding a conclusion. I'll put that on my list and hopefully get to it sometime in the near future. |
I saw a question on StackOverflow that asked about validating OpenAPI documents with a custom JSON Schema dialect. I pointed them toward this blog post that answers part of their question, but I realized there are some brief code examples that use an old version of
@hyperjump/json-schema, so I wanted to update those examples.