Ethan
Ethan
following #13 I have noticed a couple other issues, all of which I've fixed by refactoring `.parse`. - a badly formed Authorization header results in the rather unuseful error `NoMethodError:...
the symbolization of arbitrary user-supplied strings is a DoS / memory exhaustion vulnerability. this patch limits the symbols which SimpleOAuth uses for keys in the .parse method to those that...
Per discussion at https://github.com/json-schema-org/JSON-Schema-Test-Suite/pull/360 and https://github.com/json-schema-org/JSON-Schema-Test-Suite/pull/509#discussion_r700744243 The test suite sanity checker should collects all the $ids used in tests and verify they're unique, to make it easier on implementers whose...
I think this is probably what was intended - I don't see any reason for the arrays in this example to be nested. If I'm wrong and this is how...
I have started writing a collection of schemas that violate some part of JSON schema's specifications or are in some way vexatious to an implementation. This is a topic that...
### System information Type | Version/Name --- | --- Distribution Name | Fedora Distribution Version | 36 Kernel Version | 6.1.6-100 Architecture | x86_64 OpenZFS Version | zfs-2.1.8-1 ### Describe...
Amends https://github.com/simplecov-ruby/simplecov/pull/1035/commits/1cc7650454fc7c53e7a724941662c3e9d3329ccc from #1035 Another option would be to just call Coverage.start unconditionally and rescue the RuntimeError it now raises when already started.
Fixes https://github.com/json-schema-org/json-schema-spec/issues/1480 to omit the sentence about omitting the keyword, as `allOf` etc do. Also fixes a small markdown error while I'm touching that section.
After traversing a `$ref` that contains a fragment, does the evaluation path of the resolved schema include the path between the document or resource root and the subschema indicated by...
per https://github.com/json-schema-org/json-schema-spec/issues/1347 https://github.com/json-schema-org/json-schema-spec/pull/1351