fails to parse .jsbeautifyrc if $schema specified
See original GitHub issue- Operating System (+Version): Microsoft Windows [Version 10.0.15063]
- VS Code Version: 1.23.1
- beautify Version: 1.3.0
.jsbeautifyrc
{
"$schema": "http://json.schemastore.org/jsbeautifyrc",
...
}
Action performed
Format json file with HookyQR.beautifyFile
command
Expected results
File is formatted
Actual results
Error…
Found a .jsbeautifyrc file [c:\src\MyRepo\.jsbeautifyrc], but it didn’t parse correctly.
Removing the $schema line from .jsbeautifyrc results in expected behavior.
Issue Analytics
- State:
- Created 5 years ago
- Comments:5 (1 by maintainers)
Top Results From Across the Web
Ask Question - Stack Overflow
Unable to parse content from 'http://json.schemastore.org/prettierrc': Parse error at offset 0. (768) · Ask Question. Asked 2 years, 1 month ago.
Read more >Beautify - Visual Studio Marketplace
The schema indicates which beautifier each of the settings pertains to. The .jsbeautifyrc config parser accepts sub elements of html , js and ......
Read more >Guide To JSON Schema - HailBytes
JSON Schema is a useful tool for verifying JSON data structure. To specify the structure of JSON, use a JSON-based format. Its purpose...
Read more >cli - Go Packages
Parse reads the configuration file and returns a gnorm config value. ... If no pairs are specified, schemas will not be rendered.
Read more >How to enable js-beautify in Visual Studio Code - Morioh
The schema indicates which beautifier each of the settings pertains to. The .jsbeautifyrc config parser accepts sub elements of html , js and...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Few years later: @jcklpe, you have a trailing comma at
"pre",
In my case, there was a trailing comma
,
!!!