Skip to content
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

Consistent syntax highlighting in API walkthrough #4542

Merged
merged 1 commit into from
May 14, 2024

Conversation

pkel-kn
Copy link
Contributor

@pkel-kn pkel-kn commented May 14, 2024

This PR improves the syntax highlightling of your API walkthrough documentation page. Without this change, the individual snippets are recognized as arbitrary language, rendering it hard or impossible to read. The following screenshot shows an extreme case where a shell command is highlighted as CSS with important bits blacked out.

image

Consistent syntax highlighting in API walkthrough
@fgalan
Copy link
Member

fgalan commented May 14, 2024

Note that in https://github.com/telefonicaid/fiware-orion/blob/master/doc/manuals/user/walkthrough_apiv2.md the Markdown document renders correctly.

imagen

I understand the fix is for RTD rendeing at https://fiware-orion.readthedocs.io/en/master/user/walkthrough_apiv2.html

Currently, we recommend Markdown document over RTD, but of course the fix is welcome :). Thanks!

Copy link
Member

@fgalan fgalan left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

@fgalan fgalan merged commit 0b800a6 into telefonicaid:master May 14, 2024
12 checks passed
@pkel-kn
Copy link
Contributor Author

pkel-kn commented May 14, 2024

Currently, we recommend Markdown document over RTD ...

That's not obvious! All links on github landing page point to readthedocs. Also web-search for orion prominently shows the readthedocs page.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants