-
-
Notifications
You must be signed in to change notification settings - Fork 4.3k
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
feat(json): add jsonc to aliases and use it to find parser in markdown embed #4734
feat(json): add jsonc to aliases and use it to find parser in markdown embed #4734
Conversation
Can you add a test with a |
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The fields might be useful for integrators, so I don't think we should remove them. I don't think it's the end of the world that jsonc doesn't give the right linguist id in this case.
Context: #4734 (comment) Languages should be easy to maintain now.
Can you fix the merge conflicts? |
I'm still waiting for github-linguist/linguist#4171 so that I can update linguist-languages then use it here. (Marked as WIP to avoid confusing.) |
Updated to use |
JSON
andJSON with Comments
are different languages inlinguist
, but I think it's fine to just add.jsonc
toJSON
'sextensions
here since we treat them the same, thoughts?(Actually I think we should remove those unrelated fields since it's hard to maintain, for example:-> #4741JSON
andJSON with Comments
have differentlinguistLanguageId
.)Closes #4611