You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Description
Code Samples (for example curl "api_endpoint_here" \ -H "Authorization: meowmeowmeow") with httpsnipets are not appearing on Slate. I use the widdershins API to convert the .json file to html.md , and for show on slate request examples (curl, request or unirest ).
I use the config options.language_clients = [...], on my JS file, but no response is showed in slate, Although the language clients are visible on the markdown file generated config parameters on the header of the file, which I think it means that the configuration on the JS file was OK.
here is my JS file:
[YES] - I have checked that my input document is valid OpenAPI 2.0/3.0.x or AsyncAPI 1.x
To Reproduce
Steps to reproduce the behavior:
Once with the JS above is created, in CLI execute this for generate the markdown file : node Code.JS
Then replace on my Slate/source directory the file index.html existing for this one called the same name
Run docker with : docker run --rm --name slate -p 4567:4567 -v ${pwd}:/srv/slate/source slatedocs/slate serve
My input file:
See error: In the entire file doesn't appear a markdown code sample about how generate a curl response or somet index.html.md
Expected behavior
It should appear on the right side of the web browser a request body parameter or something like the Slate demo shows:
Description
Code Samples (for example curl "api_endpoint_here" \ -H "Authorization: meowmeowmeow") with httpsnipets are not appearing on Slate. I use the widdershins API to convert the .json file to html.md , and for show on slate request examples (curl, request or unirest ).
I use the config options.language_clients = [...], on my JS file, but no response is showed in slate, Although the language clients are visible on the markdown file generated config parameters on the header of the file, which I think it means that the configuration on the JS file was OK.
here is my JS file:
To Reproduce
Steps to reproduce the behavior:
index.html.md
Expected behavior
It should appear on the right side of the web browser a request body parameter or something like the Slate demo shows:
curl "http://example.com/api/kittens"
-H "Authorization: meowmeowmeow"
Screenshots
Versions:
The text was updated successfully, but these errors were encountered: