would recommend to ship a JSON with comments filetype from the start because it does seem to be somewhat common to me (mostly due to MS's VS Code which popularized)...

Sure, like "JSON (strict)" filetype using the real JSON lexer, and then a custom filetype "JSON (loose)" inheriting from the Javascript lexer like the current JSON custom filetype does.

—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub, or unsubscribe.