-
Notifications
You must be signed in to change notification settings - Fork 5
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
JSON #131
Comments
While I have not thought about json specifically, I did consider xml at one point. Json should be simpler than XML. One thing that would be needed would be a format-preserving Json parser and serialiser (e.g. not change newlines, indentation, no reformatting numbers, etc). For INI files I wrote my own code for this, but I'd rather not for Json as it is a more complex format. I also don't have a personal need for this, and this is a hobby project. So, contributions are welcome. If anyone is interested I'm willing to discuss the design (the first new format to support will be the hardest design-wise, as we need to make the code generic over the file format). |
So I had a think about what would be needed: JSON
Other formatsSide note about about XML (since I also considered this case): XML would be more complicated: you may not have unique keys, you can have text as siblings to nodes, you have attributes on nodes (not just contents) etc. Side note about toml: |
Is your feature request related to a problem? Please describe.
Thank you for working on this useful project! I was wondering whether you'd consider adding support for JSON files?
Describe the solution you'd like
Initially it could be something basic, like just a list of paths to ignore.
Round-tripping JSON shouldn't be too difficult, and a lexer + parser that retains trivia should let you retain the same formatting on output.
Describe alternatives you've considered
N/A
Additional context
The text was updated successfully, but these errors were encountered: