Allow .cson suffix-free files to be parsed

Question

Allow .cson suffix-free files to be parsed

Closed this issue 5 years ago · 4 comments

I'm trying to use CSON for a config file I'm naming .bzrc.

I'm using parseFileSync and getting this error:

[Error: CSON.parseFileSync: Unknown extension type for /Users/gsuntop/.bzrc]

Renaming to .bzrc.cson works as expected, but I'd prefer not to use this suffix. Can non-suffixed files be allowed to work? Thanks!

Answer 1 · 2014-08-11T16:53:25.000Z

As a side note, you should follow the XDG standard and use ~/.config. So something like ~/.config/bz/bzrc.

Answer 2 · 2014-08-22T22:31:38.000Z

Yeah I agree. On a side-note, related to this, can you please accept stdin as valid input? I'd expect json2cson <<< '"foo": "bar", "baz": {"bam": [1,2,3,4]}' or the likes echo '...' | json2cson to work. Or at the least a -s for string input would be nice.

Answer 3 · 2015-02-06T03:18:45.000Z

Can someone send a pull request for this and I'll review.

Answer 4 · 2019-07-20T05:06:01.000Z

Closing due to lack of initiative on this issue showing a lack of value (cost vs benefit) for this issue