andyyaldoo / vscode-json Goto Github PK

May I create a PR for support JSON5 format? Currently this repo is using json-bigint. If change to json5, will lost bigint feature. Or should I fork the repo and create a new vscode extension?

• JSON5 for Human
• json5 on npm

Following is a JSON5 example:

{
  // comments
  unquoted: 'and you can quote me on that',
  singleQuotes: 'I can use "double quotes" here',
  lineBreaks: "Look, Mom! \
No \\n's!",
  hexadecimal: 0xdecaf,
  leadingDecimalPoint: .8675309, andTrailing: 8675309.,
  positiveSign: +1,
  trailingComma: 'in objects', andIn: ['arrays',],
  "backwardsCompatible": "with JSON",
}

Tried running on very simple json file, highlighted text \\storage\example\path, hit ctrl+shift+P (command palette) triggered "vscode-json: Escape" and nothing happened.

Thank you for this extension, I am using Codium and I would appreciate to be able to install it from the Open VSX market.

Unfortunately, as Microsoft prohibits usages of the Microsoft marketplace by any other products or redistribution of .vsix files from it, in order to use VS Code extensions in non-Microsoft products, we kindly ask that you take ownership of the VS Code extension namespace in Open VSX and publish this extension on Open VSX.

What is Open VSX? Why does it exist?

Open VSX is a vendor neutral alternative to the MS marketplace used by most other derivatives of VS Code like VSCodium, Gitpod, OpenVSCode, Theia-based IDEs, and so on.

You can read on about Open VSX at the Eclipse Foundation's Open VSX FAQ.

How can you publish to Open VSX?

The docs to publish an extension can be found here. This process is straightforward and shouldn't take too long. Essentially, you need an authentication token and to execute the ovsx publish command to publish your extension. There's also a doc explaining the whole process with an example GitHub Action workflow.

There may be use cases that you want to format a block of selected text rather than the whole file. The current version does not support that yet.

The problem occurs both during use Uglify and Beautify on json file with large numbers.

Starting values: {"id1":365247355169013770,"id2":367559095164600330}
Result after use:{"id1":365247355169013760,"id2":367559095164600300}

Extension version: 1.4.2

I might look into contributing this if I find the time later.

What I am thinking is that it would be something similar to the following python code

>>> json.dumps({'asdf': 'jkl', '2': 'two'})
'{"asdf": "jkl", "2": "two"}'
>>> json.dumps({'asdf': 'jkl', '2': 'two'}, sort_keys=True)
'{"2": "two", "asdf": "jkl"}'
>>>