# Add support for hljs aliases for code hints

**URL:** <https://meta.discourse.org/t/add-support-for-hljs-aliases-for-code-hints/81298>\
**Category:** Feature\
**Tags:** pr-welcome\
**Created:** [February 23, 2018, 10:52am UTC](https://meta.discourse.org/t/add-support-for-hljs-aliases-for-code-hints/81298 "2018-02-23T10:52:19Z")\
**Posts on this page:** 1\
**Showing post:** 3

<div class="post-metadata">

**Author:** ![Aerijo](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/aerijo/32/105751_2.png) [@Aerijo](https://meta.discourse.org/u/Aerijo)\
**Post date:** [February 23, 2018, 9:20pm UTC](https://meta.discourse.org/t/add-support-for-hljs-aliases-for-code-hints/81298/3 "2018-02-23T21:20:21Z")

</div>

Thanks for the pointer. I followed the link, and it says

> The list of supported language classes is available in the [class reference](http://highlightjs.readthedocs.io/en/latest/css-classes-reference.html)

The class reference it links to has a table of supported languages, and recognised keywords to select each one. I believe the “bottleneck” is happening on the discourse side, where it’s only passing a limited subset of language keywords to Highlight.JS.

In fact, it would be great if all the supported keywords were allowed, as some look quite interesting.

FYI, it has `js` for JavaScript, and `c++` for C++. So I think this is definitely worth looking into.

---

_[View the full topic](https://meta.discourse.org/t/add-support-for-hljs-aliases-for-code-hints/81298)._