You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository was archived by the owner on Aug 31, 2023. It is now read-only.
ematipico opened this issue
Apr 5, 2022
· 2 comments
· Fixed by #3836
Assignees
Labels
A-ParserArea: parserI-StaffImplementation: should be in charge of a core member of the teamL-JSONLanguage: JSONS-PlannedStatus: planned by the team, but not in the short term
We are going to use this issue to track the various work around JSON. We don't plan, for the time being, to support super languages, like JSONC, which is the format used by TypeScript.
create a json.ungram file where we will slowly implement new grammars
create a rome_json_syntax crate, where we will have all things related to the JSON syntax, generated code too
expand the codegen of the grammar to include JSON too
evaluate how to implement the parser, lexer, etc. (it will require a separate discussion)
The text was updated successfully, but these errors were encountered:
Hey so I wrote a Json parser in rust not too long ago so I could maybe look into some of that if you'd like ? I feel like I understand the format pretty well.
IDK about the project setup though so I'd like some help with that :)
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Labels
A-ParserArea: parserI-StaffImplementation: should be in charge of a core member of the teamL-JSONLanguage: JSONS-PlannedStatus: planned by the team, but not in the short term
Description
We are going to use this issue to track the various work around JSON. We don't plan, for the time being, to support super languages, like JSONC, which is the format used by TypeScript.
json.ungram
file where we will slowly implement new grammarsrome_json_syntax
crate, where we will have all things related to the JSON syntax, generated code tooThe text was updated successfully, but these errors were encountered: