-
Notifications
You must be signed in to change notification settings - Fork 0
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
openapi snippets are not rendering #43
Comments
this blocks fully addressing aep-dev/aeps#224 |
Another note - it would be great if the selector syntax could somehow selectively choose a sub-element. For example in OAS, the list and create endpoints are both mounted under the resource collection name. For example, the following syntax:
On a complete OAS example renders: It'd be great if you could just select the
that will implicitly include the parent so that it's easy to figure out the position? |
Adding oas examples for create. This also tests out the pattern outlined in aep-dev#230 - adding a generated oas.yaml and use selective elements from it as an example, which looks to work pretty well. There is a blocker on aep-dev/site-generator#43 to allow for support from a json-path like structure to target sub-elements, but this will at least allow for selective guidance to be easily added.
Adding oas examples for create. This also tests out the pattern outlined in aep-dev#230 - adding a generated oas.yaml and use selective elements from it as an example, which looks to work pretty well. There is a blocker on aep-dev/site-generator#43 to allow for support from a json-path like structure to target sub-elements, but this will at least allow for selective guidance to be easily added.
Adding oas examples for create. This also tests out the pattern outlined in aep-dev#230 - adding a generated oas.yaml and use selective elements from it as an example, which looks to work pretty well. There is a blocker on aep-dev/site-generator#43 to allow for support from a json-path like structure to target sub-elements, but this will at least allow for selective guidance to be easily added.
Adding oas examples for create. This also tests out the pattern outlined in aep-dev#230 - adding a generated oas.yaml and use selective elements from it as an example, which looks to work pretty well. There is a blocker on aep-dev/site-generator#43 to allow for support from a json-path like structure to target sub-elements, but this will at least allow for selective guidance to be easily added.
Adding oas examples for create. This also tests out the pattern outlined in aep-dev#230 - adding a generated oas.yaml and use selective elements from it as an example, which looks to work pretty well. There is a blocker on aep-dev/site-generator#43 to allow for support from a json-path like structure to target sub-elements, but this will at least allow for selective guidance to be easily added.
Adding oas examples for create. This also tests out the pattern outlined in #230 - adding a generated oas.yaml and use selective elements from it as an example, which looks to work pretty well. There is a blocker on aep-dev/site-generator#43 to allow for support from a json-path like structure to target sub-elements, but this will at least allow for selective guidance to be easily added. --------- Co-authored-by: Richard Frankel <[email protected]>
example: http://localhost:4002/151#interface-definitions.
compare the original site, and the beta generator.
The text was updated successfully, but these errors were encountered: