oxfmt: Make `.oxfmtrc.jsonc` the default instead of `.json`?

[leaysgur]

Suggestion from:

Since this is a new tool, In my opinion, it'd be better to default to .oxfmtrc.jsonc, which forces comment support, and provides better ide support (else you get your ide complaining about comments in .json files (which aren't technichally supported).
#14398 (comment)

Backgroud:

• oxfmt auto search config file if not specified by -c or --config
• In this case, .oxfmtrc.json is the default (not .jsonc)

---

Personally, I agree with this suggestion.

(To be more precise, IMO, I'm open to even dropping comment support for .json files, but I tolerate it because of examples like tsconfig.json. 😶‍🌫️)

However, I also feel that the .jsonc extension has yet to gain widespread adoption.
(Even VSCode apparently has an association setting that lets you keep the .json extension while having it interpreted as .jsonc!)

Therefore, as a compromise, I'm considering reverting to the behavior implemented in the initial PR, which searching for both .json and .jsonc by default.

Or, just keep it as-is, only .json.

[nrayburn-tech]

For what it’s worth, I don’t think IntelliJ has a jsonc option. It has JSON and json5. You can use JSON and disable the warning about comments, which works but isn’t ideal.

Just something to note on editor support.

[ghiscoding]

another thing to also be aware is that as far as I know, JSON Schema is only supported via .json extension

[leaysgur]

After some discussion, I decided to:

• Search both .jsonc and .json
• First wins and .json is the first

NOTE: dprint also follows this behavior
https://github.com/dprint/dprint/blob/4cf6297638b301f4371cc9d9a7f964b2e88ba9d5/crates/dprint/src/configuration/resolve_main_config_path.rs#L77

[leaysgur]

#14848