Matthew Pope
Matthew Pope
Suppose I have the following schema: ``` $ion_schema_2_0 type::{ name: Foo, fields: { a: { fields: { x: int, y: int } }, b: int, } } type::{ name: Bar,...
> We should probably do something similar to `ion-rust` where we have a feature matrix in the workflow—or at least run the tests with and without `--all-features`. Doesn't need to...
I have been musing about a potential problem with the "beta" namespace. Namely, what do we want to do if, e.g. `ion beta schema validate` becomes stable, but there's a...
The `jq` tool is cited as one of the reasons for wanting to downconvert to JSON in #40. If `ion-cli` had a subcommand with similar functionality, it would be one...
Given an Ion file such as ``` a b c ``` the `ion-cli beta schema validate` command will perform separate validations on each value in this file instead of reading...
When any number of types have a circular "is-a" relationship it results in a `StackOverflowException` during validation. Ideally, it should result in an `InvalidSchemaException` when loading the schema. See https://github.com/amazon-ion/ion-schema-rust/issues/205...
>Should we look for another version marker and reenter the parsing loop if we find one? No, I don't think so. There's a bunch of issues that make it undesirable...
Having a properly typed model will make it nicer to manipulate the schema definitions for things such as: * converting to/from other schema formats * comparing two schemas * writing...
A type constructed with `newType()` should have the same `user_reserved_fields` validation as the schema that it is derived from. ```kotlin @Test fun gh_issue_232_repro() { val iss = IonSchemaSystemBuilder.standard().build() val schema...