-
Notifications
You must be signed in to change notification settings - Fork 487
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
Editor: Data types misses type: object #487
Comments
FYI - I've fixed this in the |
This has been fixed and committed - should be all set for the next release. |
Thanks for the error report! |
@EricWittmann I see the issue is still here, at least something very similar, for the responses. Shouldn't I be able to choose "object" data type here? |
At the moment, apicurio doesn't support inline object definitions. So you would need to create a global data type and then refer to it in the |
Any update on this issue? It's the last thing I need before I rewrite all my documentation using this tool :) |
Which aspect of this issue do you need? Are you referring to inline object definitions? If so, why are reusable definitions not an acceptable alternative? I'd love to know the use-case so that can influence the priority of the feature. |
we already have documentation wrote in OpenAPI manually or by other tools that we would like to reuse. inline object definition is common feature, at least I feel like this and it's needed for other tools compatibility. second problem is that following your advice we fastly have a lot of object definitions that are in real only one-time used definitions. it's make definitions list too long and distracts attention from really useful, commonly used structures in our apis. e.g. instead of have |
OK thanks for the feedback, @psychowico - I'm going to open a new feature request to add better support for inline schemas. I think your reasons for wanting that feature are good. :) |
Just referencing your new feature request in case someone is looking for it: #744 |
When I create a new data type (schemas under components), It doesn't add
type:object
to schema definitionThe text was updated successfully, but these errors were encountered: