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
I noticed that the ReDoc docs give a list of supported languages to use for the x-code-samples blog, but in practice, the list is slightly different to get the right syntax. For instance, here it is with python:
and here's the same with Python:
The first one looks like it has the correct formatting (the second one uses "fallback" formatting), but it looks a bit sloppy to have "python" be lowercase in the sidebar. Could you possibly update the list of supported languages based on the package being used to highlight the code?
Furthermore, may I propose having a new field for each code sample like "label"? That would be useful here (would have lang: python, label: Python) and for other scenarios, say if I'd like to give to JavaScript samples, one in the browser w/fetch and one using some Node library.
Happy to send a PR out if you think that's fine, @RomanGotsiy (though you'd probably do it faster as it should be an easy change :D).
The text was updated successfully, but these errors were encountered:
I noticed that the ReDoc docs give a list of supported languages to use for the
x-code-samples
blog, but in practice, the list is slightly different to get the right syntax. For instance, here it is withpython
:and here's the same with
Python
:The first one looks like it has the correct formatting (the second one uses "fallback" formatting), but it looks a bit sloppy to have "python" be lowercase in the sidebar. Could you possibly update the list of supported languages based on the package being used to highlight the code?
Furthermore, may I propose having a new field for each code sample like
"label"
? That would be useful here (would havelang: python, label: Python
) and for other scenarios, say if I'd like to give to JavaScript samples, one in the browser w/fetch
and one using some Node library.Happy to send a PR out if you think that's fine, @RomanGotsiy (though you'd probably do it faster as it should be an easy change :D).
The text was updated successfully, but these errors were encountered: