-
-
Notifications
You must be signed in to change notification settings - Fork 5.8k
Fix Erlang and Elixir highlight mappings #7044
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
Conversation
Please reformat ( |
Done. A friend also made me aware that hightlight.js has an "erl" alias for erlang, so that one could be moved up to the upper mapping. The three other are less lucky. Would you prefer that? |
Codecov Report
@@ Coverage Diff @@
## master #7044 +/- ##
==========================================
- Coverage 41.72% 41.72% -0.01%
==========================================
Files 443 443
Lines 60149 60149
==========================================
- Hits 25099 25097 -2
- Misses 31774 31776 +2
Partials 3276 3276
Continue to review full report at Codecov.
|
Yes please move erl up if it works with our used version |
Moved ".erl" up to be in the same place as ".erlang" was before. Not sure what the ordering is. Tested with the shipped highlight.js - works as expected. |
Hi,
Without these changes, the highlighting language determination for both Erlang (.erl, .escript) and Elixir (.ex, .exs) files is left up to a dice roll -- sometimes it is typescript, some other times actionscript. Exciting.
I do not believe ".erlang" and ".elixir" to be extensions used wildly in the wild.
I realize this replaces a single entry with two for each of the languages, and .escript is not even that common and could be left out.
Thanks.