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

Use / implement JsonNet syntax highlighter for PrismJS #970

Open
3 of 6 tasks
aeneasr opened this issue Aug 29, 2022 · 1 comment
Open
3 of 6 tasks

Use / implement JsonNet syntax highlighter for PrismJS #970

aeneasr opened this issue Aug 29, 2022 · 1 comment
Labels
feat New feature or request.

Comments

@aeneasr
Copy link
Member

aeneasr commented Aug 29, 2022

Preflight checklist

Describe your problem

Some of our code examples are written in JsonNet, which is not (yet) supported by PrismJS. A quick search on Google did not surface a JsonNet plugin for PrimsJS. It is still a good idea to ask the JsonNet maintainers whether they know if such a plugin exists or not.

Describe your ideal solution

JsonNet code examples should be correctly formatted.

Workarounds or alternatives

If we for sure can not find an existing plugin for this, we might consider writing one ourselves.

We could also try to use jsonnet as an alias for json, to get some interim code-highlighting.

Version

master

Additional Context

No response

@aeneasr aeneasr added the feat New feature or request. label Aug 29, 2022
@github-actions
Copy link

Hello contributors!

I am marking this issue as stale as it has not received any engagement from the community or maintainers for a year. That does not imply that the issue has no merit! If you feel strongly about this issue

  • open a PR referencing and resolving the issue;
  • leave a comment on it and discuss ideas on how you could contribute towards resolving it;
  • leave a comment and describe in detail why this issue is critical for your use case;
  • open a new issue with updated details and a plan for resolving the issue.

Throughout its lifetime, Ory has received over 10.000 issues and PRs. To sustain that growth, we need to prioritize and focus on issues that are important to the community. A good indication of importance, and thus priority, is activity on a topic.

Unfortunately, burnout has become a topic of concern amongst open-source projects.

It can lead to severe personal and health issues as well as opening catastrophic attack vectors.

The motivation for this automation is to help prioritize issues in the backlog and not ignore, reject, or belittle anyone.

If this issue was marked as stale erroneously you can exempt it by adding the backlog label, assigning someone, or setting a milestone for it.

Thank you for your understanding and to anyone who participated in the conversation! And as written above, please do participate in the conversation if this topic is important to you!

Thank you 🙏✌️

@github-actions github-actions bot added the stale Feedback from one or more authors is required to proceed. label Aug 30, 2023
@aeneasr aeneasr removed the stale Feedback from one or more authors is required to proceed. label Aug 30, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
feat New feature or request.
Projects
None yet
Development

No branches or pull requests

1 participant