Because the settings.json may be commented, it is not considered as a "real" JSON formatted file. The backend uses an inner regex to parse the comments out and this implies to escape the / (slash) character included in the fields values (eg. "http://localhost" must be "http:\/\/localhost").
Perharps updating the regex or using a Json lib would avoid this problem
Because the settings.json may be commented, it is not considered as a "real" JSON formatted file. The backend uses an inner regex to parse the comments out and this implies to escape the / (slash) character included in the fields values (eg. "http://localhost" must be "http:\/\/localhost").
Perharps updating the regex or using a Json lib would avoid this problem