Open hahn-kev opened 1 year ago
When the translations are transformed back into the respective file format, information such as comments would be lost anyway.
Apart from the comment function, why should normal json files be treated as json5?
We're using the multi line string feature in json5 as some of our translations are quite long and some team members edit the files manually or use vscode.
We've got some json files that we treat as json5, but they're still just
en.json
and the extension doesn't like that. It'll read the files just fine, but when I modify one it'll write out a fileen.json5
even though it's readingen.json
, it sounds like the file writer isn't following the pattern*.json
and just always writes out.json5
files. Can this be changed?