I'm aware .json is the proper extension for JSON, but I'm frequently forced to work with other user's JSON files that are .txt. I understand the defaults for an "open dialog" restricting to documents with the preferred extension, but it would be nice if there were some sort of over-ride to force Smart JSON Editor to open/save documents that are valid JSON but may not be saved with the right extension. I can't just fix the extensions, as of course code interacts with the files.
JSON editor is very picky about file extensions.
I'm aware .json is the proper extension for JSON, but I'm frequently forced to work with other user's JSON files that are .txt. I understand the defaults for an "open dialog" restricting to documents with the preferred extension, but it would be nice if there were some sort of over-ride to force Smart JSON Editor to open/save documents that are valid JSON but may not be saved with the right extension. I can't just fix the extensions, as of course code interacts with the files.