json:S1578 naming convention rule is too narrow

[thw0rted]

JSON is a broadly adopted standard and is consumed by a wide variety of languages. Several of the constraints in json:S1578 are counter to conventions in certain languages -- for example, some languages encourage underscore_case over camelCase. I came here to file this issue because a number of technologies that I use encourage the use of multiple dot-separated name parts, e.g. tsconfig.aot.json or production.config.json.

I'm all for enforcing opinionated design if you're making your own language, but this rule describes a "universally-desirable" naming convention that simply does not exist.

[racodond]

Hi @thw0rted,

I don't maintain this plugin anymore. See https://github.com/racodond/sonar-json-plugin#disclaimer
Feel free to fork or take over.

Thank you

David