Remi Rampin
Remi Rampin
I ran into this, trying to use `openapi-core`. It first runs the spec through `openapi-spec-validator`, which fails on some cryptic `jsonschema` `TypeError` (doing `re.search()` on an int instead of str)....
I ran into this using `requests` and `RequestsOpenAPIRequest`, when the server sends `Content-type` instead of `Content-Type`. :roll_eyes:
There's also https://github.com/yannh/kubernetes-json-schema used by Kubeconform
This hasn't been updated in years, posting here does nothing. See https://github.com/yannh/kubernetes-json-schema for an up to date repository.
(@arfon: I see the pre-review issue has been closed, but we are missing another reviewer; is that protocol?)
I have taken a first look at the repositories. Some notes: * **General**: `shed` is taken on PyPI, by https://github.com/Zac-HD/shed. It might be beneficial to use a unique name, such...
I also note that the main contributors of the code are not watching the GitHub repository, which will probably cause problems in the case of external contributions or reports.
Thanks @arfon, I must say I haven't been prioritizing this since we are missing the second reviewer. I was also hoping some of my points in https://github.com/openjournals/joss-reviews/issues/3119#issuecomment-809781527 would be addressed,...
Because decoding `PathBuf` is decoding `Vec`, I'm assuming that docopt mistakes a `PathBuf` option for a `u8` option that can be passed multiple times (note that `Vec` still doesn't work).