Karen Etheridge

I was just installing my toolchain on a new 5.8.6 perlbrew and I had trouble installing App::Cmd -- but the third attempt to install it succeeded. I use HARNESS_OPTIONS=j9 in...

deps graph always displays 'core' and no test results for core modules, even if the version is important

1

Here's an example: http://deps.cpantesters.org/?module=Dist%3A%3AZilla%3A%3APluginBundle%3A%3AAuthor%3A%3AETHER&perl=5.10&os=any+OS That's Dist::Zilla::PluginBundle::Author::ETHER at perl 5.10.x. Test::More is still shown as "core module" with no test results, even though Test::More in 5.10.0 was at 0.72 and in...

Mojo::URL accepts invalid schemes

8

* Mojolicious version: 8.57 ### Steps to reproduce the behavior `Mojo::URL->new("bar,baz:foo")` ### Expected behavior An error in `parse`, or construction of an empty object, because "bar,baz" is not a valid...

This improves readability by making it easier to find the methods that aren't simply shortcuts to particular headers. I have confirmed that the headers listed in %NAMES exactly matches those...

https://spec.openapis.org/oas/v3.1.0#fixed-fields-16

conflicting order of operations when applying Content-Encoding and Content-Type headers

3

The specification describes how to handle requests/responses with both a Content-Type and Content-Encoding header: " JSON Schema offers a contentEncoding keyword, which may be used to specify the Content-Encoding for...

- a JSON Schema evaluator (draft7, draft2019-09, draft2020-12) - https://github.com/karenetheridge/JSON-Schema-Modern, https://metacpan.org/pod/JSON::Schema::Modern - an OpenAPI request/response validator (only v3.1 supported, not v3.0) - https://github.com/karenetheridge/OpenAPI-Modern, https://metacpan.org/pod/OpenAPI::Modern

prohibit the use of fragments in $id and $schema

24

We permit empty fragments in `$id`, and say nothing at all about fragments in `$schema`. IMO we should prohibit all kinds of fragments in both keywords' URIs. cross-reference: https://github.com/OAI/OpenAPI-Specification/issues/2433#issuecomment-756389903

resolve contradictions in the described behaviour of "additionalProperties" and "items"

15

Wording has been reverted to that of draft7, before annotations existed, and the behaviour was clearly in terms of the presence of adjacent "properties" and "patternProperties" keywords, not their evaluation...

resolve ambiguity regarding annotation inclusion in failed validation results

26

The spec says (https://json-schema.org/draft/2019-09/json-schema-core.html#rfc.section.7.7.1.2): > Schema objects that produce a false assertion result MUST NOT produce any annotation results, whether from their own keywords or from keywords in subschemas. However,...