There is absolutely no need to create a second JSON syntax highlighting wordfile if just one more file extension needs to be recognized for syntax highlighting JSON files with a different file extension than JSON. The additional file extension must be just added to json.uew file according to the steps of first list in my previous post.
I have just found out with some tests with UE v22.214.171.124 that a file is parsed for JSON manager view if its file extension is JSON independent on syntax highlighting of the file.
When deleting json.uew wordfile or renaming its file extension while UE is not running and then starting UE with loading a *.json file, the file is not syntax highlighted, but JSON manager view shows the data in tree view.
On the other hand on appending for example file extension TXT on first line of wordfile json.uew and opening a *.txt file containing JSON structured data, the file is syntax highlighted as JSON file, but is not JSON parsed and therefore JSON manager view remains empty.
However, clicking with secondary (right) mouse button into JSON manager view to open its context menu and clicking with primary (left) mouse button on context menu item Parse document results in JSON parsing of active document independent on applied syntax highlighting.
I have sent a feature request by email to IDM support suggesting to run JSON parser not only on *.json files automatically (according to JSON related settings in configuration), but also on all files which are syntax highlighted with a language having language marker JSON_LANG. An alternate suggestion would be adding to JSON configuration dialog an edit field on which users can specify a semicolon separated list of file extensions and file names like .json;.config;ApplicationName.cfg. Each name of a file (file name + file extension) ending case-insensitive with one of those strings should be interpreted as JSON file. I have added this second suggestion into same feature request email. Of course my request is just one of millions of users. So it is necessary that other users (especially those representing more licenses than 1) request such an enhancement for automatic JSON parsing, too.