Open gbowne1 opened 1 month ago
How much of this is feasible without making the package too bloated?
So we can make library one package and then apps be seperate, what also probably be more reliable for the end user, as in that case if library doesnt package apps also wont package
Agreed. let me know what you think on these features.
- JSON Serialization/Deserialization
- Not sure about this one becuase its kindoff alredy implement
- also can be considered as plain old data seriasilation
- Able to use JSON5
- would priritize this as it follows json theme
- My main question here is "In House" implementation or use pyjson5?
- Compliant with ECMA262
- havent read the spec yet so could be useful
- Able to parse partial and or faulty strings
- would leave this perhaps a feature that user has to bring in via the patches as it could be quite unstable
- logging utility
- very usefull for cli users
- Able to fetch from URL/URI
- would leave for later since it will require rework of cli app
- API tooling
- hostable api?
- Able to lint JSON/JSONC, possible formatting
- theres prettier, eslint, etc... so is it really necessary?
- Generate random JSON for testing purposes/mocking
- will be good for users testing in offline environments
- Generate a CMakeLists.txt file from a compile_commands.json
- can be quite complex, as there can be compile_commands.json per cmake project
- Generate .xls/xlsx from JSON
- not sure how since its basically propriatery format
- Able to split large JSON files into chunks
- sure, noone like big github api response dumps (i dont know how much have worked around github api but it can have up to 5mb dumps)
- Able to 'flatten' nested json
- would leave it for later
- work with .jsonl format
- quite easy without validation
- works with jsonp format
- padded or pretty format?
- numpy arrays
- not sure havent used numpy
- hash generation of json objects
- good idea, like nested sha-sum file?
I've thought about some features for JSONMaestro a little bit