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
Many languages in shiki have aliases. At this time typedoc believes that these aliases are "fakes" and manually handles the five for typescript-as-ts, javascript-as-js, and shell-as-[sh, bash, zsh] in creating the supported language list.
Shiki offers an aliases field which should be walked instead. Many other aliases, such as ruby-as-rb, python-as-py, jssm-as-fsl and so on are being missed, and the ones being manually loaded become unnecessary.
Actual Behavior
typedoc does not understand language aliases, except the five manually added to the list.
Steps to reproduce the bug
Attempt to highlight the following two blocks.
\```ruby
puts "this will work";
\```
\```rb
puts "this will not work, but should";
\```
Note: that backslash shouldn't be there, I just don't know how to quote a triple tick in a fence block
PR incoming
Environment
Typedoc version: 0.21.8
TypeScript version: irrelevant
Node.js version: irrelevant
OS: irrelevant
The text was updated successfully, but these errors were encountered:
Expected Behavior
typedoc
should understand language aliases.Many languages in shiki have aliases. At this time
typedoc
believes that these aliases are "fakes" and manually handles the five fortypescript
-as-ts
,javascript
-as-js
, andshell
-as-[sh
,bash
,zsh
] in creating the supported language list.Shiki offers an
aliases
field which should be walked instead. Many other aliases, such asruby
-as-rb
,python
-as-py
,jssm
-as-fsl
and so on are being missed, and the ones being manually loaded become unnecessary.Actual Behavior
typedoc
does not understand language aliases, except the five manually added to the list.Steps to reproduce the bug
Attempt to highlight the following two blocks.
Note: that backslash shouldn't be there, I just don't know how to quote a triple tick in a fence block
PR incoming
Environment
The text was updated successfully, but these errors were encountered: