Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

Support JSON file formatting?

See original GitHub issue

Not sure if it’s a long shot or not, but would adding .json formatting be out of scope? Would it be difficult to add?

Issue Analytics

State:
Created 7 years ago
Reactions:1
Comments:9 (6 by maintainers)

Top GitHub Comments

4reactions

lydellcommented, Jan 19, 2017

Shameless plug: https://github.com/lydell/json-stringify-pretty-compact

2reactions

jlongstercommented, Jan 19, 2017

Agreed, JSON does not have types like functions or binary expressions and so a simpler formatting (that doesn’t need the constraint-based solver here) works.

Although, I can see the case for wanting to use the same editor plugins to be formatting your package.json as you write it. The core issue is the top-level { problem. We’d need to disambiguate top-level blocks and force them into JS objects, which means we won’t allow top-level objects.

Or we could check if the filename ends in json and special case it.

I can see the it being annoying typing cmd+alt+f (or whatever in the rest of your project) but not being able to in JSON files.