Artur Maciag
Artur Maciag
Hi @robinmackaij-kadaster > The resulting dependencies are wrong: openapi-schema-validator 0.2.3 and openapi-spec-validator 0.4.0 were installed. The openapi-core dependency ranges as shown in poetry show --tree are openapi-schema-validator >=0.2.0,=0.4.0,
@diogobaeder Hi. I plan to add model factory as configuration option for now you can use `result.body. __dict__` which returns all model parameters in dict.
@sarangsbabu367 That sounds like use case for you request/response library. You should try to do this with some kind of middleware. Alternatively you can try to create custom formatter with...
It must be something with the integration. I assume you use Falcon one?
I believe it should be handled by 3tf party libraries/projects that use `openapi-spec-validator`. We can't tell openapi validator user that he should use `file://` because it depends on which [handlers](https://github.com/p1c2u/openapi-spec-validator/blob/master/openapi_spec_validator/__init__.py#L24)...
@alexanderkjeldaas hi, can you provide example spec?
Closing in favor of #423 Thank you all for your contribution.
Hi @sisp definitely interested. Feel free to propose your ideas. I added x-model extension support with possibility to use predefined models. See [x-model extension](https://openapi-core.readthedocs.io/en/latest/extensions.html#x-model).
@diogobaeder this is tricky one. I need to have #34 AnyOf supprt done first.
It will be fixed in version 0.5.x which is dependent on jsonschema4+ Version 0.4.x will support jsonschema 3 and 4.