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
{{ message }}
This repository has been archived by the owner on Apr 9, 2023. It is now read-only.
I assume you're wanting it detected as text/json or the sort. It seems from reading around (see http://stackoverflow.com/q/477816) that application/json is the way to go for json filetypes. If you want to compare against something else, you should be able to use the match_* functions which should handle aliases like text/json or the like.
There is also the problem that any valid json file is also a valid yaml and a valid toml file.
For many textual formats there is no good way to differentiate them except heuristics.
(like any php .init is a differen but similar format as py .property files which can be
equivalent to an toml file)
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Currently JSON files do not seem to be detected properly, but instead detected as
application/json
. Is this planned, or out of scope?The text was updated successfully, but these errors were encountered: