A repo for my "generic" Jsonnet code, in particular a TSV parser, and "big int" support.
WARNING: This is currently a v0.1 prototype. Don't use this for anything, unless you want to fix the bugs yourself!
The goal is to load up a TSV file in Jsonnet, parse the strings, and turn it into an array of objects. But I also wanted to support "big integers" (signed/unsigned 64-bit ints) and enums types, and there is currently no support for those in the standard Jsonnet library, so I started working on them as well.
The main downside of saving the data in a TSV file, is that it's pure data; I cannot currently "generate" data using expressions, like in Jsonnet. Eventually, I'll solve that too.
The "motivation" for the TSV parser is that my "users" will be just that, "users", not techies, so that I cannot expect them to be able to edit Jsonnet, JSON or XML. Editing a TSV file as a spreadsheet, is about as much as I can expect from them.
Currently, the following modules have working "unit tests", but some features are missing: (I decided to stick to the 3-letters module name convention of "std".)
utl: The "utility" module. log: The "logging" module. I try to collect all info/warn/errors and give them ALL at the END. int: The "big integer" module. Note: No work was done on optimizing for speed. spr: The "safe parser" module. "Safe" as in "does not crash with an error on bad user input". Note: JSON user input cannot be safely validated until Jsonnet supports regular expressions. Also supports enums and TSV files.
spr needs a lot more testing.
run:
jsonnet test.jsonnet
to check the functionality of the code.
- Check that the parsing code actually matches the regex
- Refactor code, so that all functions are public, but we separate public API from internal API so we can test the internal API too.
- Use a file called "external.libjsonnet" (or something similar) to encapsule the "external" values (files and external parameters).
- Define external schema syntax.
- Process external schema files.
- Support external schemas.
- Support "second-line" internal schema
- In the JSON output, ints must be within the supported range.
- Simplify the int API to not "take anything"
- Add "types" to lists
- Add sets
- Add maps
- Support typed:
- Boolean
- Number
- Int
- Hex
- String
- List
- Set
- Map
- Object
- Support No-Schema
- Support calls
- Support assignment
- Support comments
- Support func