-
Notifications
You must be signed in to change notification settings - Fork 292
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Support for rendering individual JSON schema #253
Comments
I would like to know about the use case here, |
My understanding is that w/ OpenAPI 3.1 both will now be aligned (see OAI/OpenAPI-Specification#1977) and OpenAPI schema will now be a superset (or vocabulary) of The use case would be to render individual JSON schema using |
Well, we arn't there yet. But, I am glad you brought it up. I have added this to our task list and will back it up with feature-request If that means its same as JSON-Schema draft 2019 then even better |
This change allow usage of <schema-tree> and <schema-table> custom element with a child <pre> block containing a JSON schema. Fixes rapi-doc#253
Act as a wrapper for schema-table and schema-tree to render inline JSON schemas Fixes rapi-doc#253
Act as a wrapper for `<schema-table>` and `<schema-tree>` to render inline JSON schemas. Fixes rapi-doc#253
please refer to my comments on the PR. |
Would really be nice to render just a json schema alone using a subcomponent of this library. |
I actually saw in #781 that this is already somewhat available in https://github.com/rapi-doc/RapiDoc/blob/master/src/json-schema-viewer.js. |
It would be nice to support rendering vanilla JSON schema in addition to OpenAPI specs.
Looking at the implementation of
<schema-tree>
and<schema-table>
, it seems that they currently get an intermediate representation of the schema thru their.data
attributes.Do you think it would be desirable to extend those components to allow passing a JSON schema thru the element body, or would you rather see another component by introduced, ex:
(using a
<pre>
would allow to fallback to just displaying the raw schema.The text was updated successfully, but these errors were encountered: