Ravi van Rooijen
Ravi van Rooijen
Title pretty much says it all :) This allows differentiating between the `uri` and `uri-reference` format. Draft-04 was [ambiguous](https://json-schema.org/understanding-json-schema/reference/string.html#resource-identifiers) in that regard, causing false-positive validation failures with some validator implementations.
**Is your feature request related to a problem? Please describe.** It's currently not possible to provide specific error messages to the `XXXOrThrow` methods. This limits these "AST assertions" to generic...
Please fill in this template. - [x] Use a meaningful title for the pull request. Include the name of the package modified. - [x] Test the change in your own...
Title says it all :) I'd recommend reviewing this per-commit. This creates a minor conflict with #86 so I'll have to adjust it. #86's testcase can be simplified with this,...
Title says it all, turns out `SNBTWriter` has been broken since 0eeca85b28c831f2febf105d0b00045540a10100 :( There current implementation is flawed in two ways: - The `PrintWriter` is left to the default system...
Title says it all :) In the spirit of #74, if `ListTag` and `ListTag.iterateType` are `Collection`-/`List`-compatible why shouldn't `CompoundTag` be `Map` compatible :) I opted to add the `Object`-typed `Map`...
Title says it all :)
I find myself often writing tests like this: ```js describe(*name*, function() { itParam(*name*, [ data ], function() { // ... }) // no other tests }) ``` I'd propose to...
It's great that we can use `${value}` inside test names, but sometimes `value` isn't a very descriptive name for a test. To get around this, I often write tests like...
Title says it all, fixes #6. This branch is based on #13, meaning it shouldn't be merged until that one's merged. I did this to avoid regressing the this-context shenanigans....