cson-parser
cson-parser copied to clipboard
groupon
Implement clean parser
Right now we are using CSR for parsing which handles a huge superset of the files we'd want to parse. We should consider implementing a clean parser for CSON as part of this repo.
├─┬ [email protected]
│ ├── [email protected] (git://github.com/michaelficarra/cscodegen.git#73fd7202ac086c26f18c9d56f025b18b3c6f5383)
│ ├─┬ [email protected]
│ │ ├── [email protected]
│ │ └── [email protected]
│ ├─┬ [email protected]
│ │ ├── [email protected]
│ │ ├── [email protected]
│ │ ├─┬ [email protected]
│ │ │ └── [email protected]
│ │ ├── [email protected]
│ │ └─┬ [email protected]
│ │ ├── [email protected]
│ │ └── [email protected]
│ ├─┬ [email protected]
│ │ └── [email protected]
│ ├─┬ [email protected]
│ │ └── [email protected]
│ └── [email protected]
Pretty much 100% of that is not used by us. But somebody who wants to parse CSON files will have to download all of it. And there's the point that CSR is in eternal beta and seems all but abandoned.
I mean, it sounds like a fine idea, but it sounds like a bunch of work that's only benefit is to make the download smaller? Is there a performance improvement?
I wouldn't expect a serious performance improvement (it's not doing that much more). But it would cut the installed size of this package in half and help defining what exactly valid CSON is (without referring to CSR implementation details). I'm not sure the initial implementation is really worth it, but it might be a fun weekend project at some point.
It would be pretty neat if it didn't choke on legal coffee-script literals that cs-redux hates on, such as
{ "comma": "first"
, "basic": "json"
}
@johan Since you know my hate for comma-first I'm sure you know that this is unlikely to make the cut if I'd be writing the parser... ;)
