Feature request: JSON5 Variables
See original GitHub issueI find myself testing various queries a lot, and when I do this, it’d be really nice if I could just comment out some query variables (preferably with cmd + /
shortcut) instead of having to delete them completely and then re-enter them when I want to test them out again.
It’s not a big deal, but it’d be nice.
Issue Analytics
- State:
- Created 5 years ago
- Reactions:2
- Comments:16 (13 by maintainers)
Top Results From Across the Web
JSON5 – JSON for Humans | JSON5
The following ECMAScript 5.1 features, which are not supported in JSON, have been extended to JSON5. ... This will create a global `JSON5`...
Read more >json5 - npm.io
This will create a global JSON5 variable. ... To report bugs or request features regarding the JSON5 data format, please submit an issue...
Read more >json5-loader - webpack
A webpack loader for parsing json5 files into JavaScript objects. Getting Started. To begin, you'll need to install json5-loader : $ npm install...
Read more >third_party/blink/renderer/platform/runtime_enabled_features ...
runtime_enabled_features.json5 ... The C++ variable name in. // blink::features ... the Blink features, for now we require the base::Feature to be enabled.
Read more >Configuration - Tauri Apps
json . Tauri also supports JSON5 and TOML files via the config-json5 and config-toml Cargo features, respectively. The JSON5 file name ...
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 FreeTop 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
Top GitHub Comments
The “Query Variables” input at the moment is JSON, so comments are not supported.
One option would be to use JSON5 instead of JSON for the variables, and we could convert it to plain old JSON before we send it to the fetcher. This seems like a great candidate for a v1 feature; what do you think @acao?
@benjie but it could lead to JSON5 that is not valid JSONC, breaking copy paste?