- Sponsor
-
Notifications
You must be signed in to change notification settings - Fork 135
How to specify custom formatter when using Flask View integration? #618
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Comments
Thanks for the report. Formatters were replaced with Format validators (this one suits your use case) and Format unmarshallers. What I forgot is to give possibility to pass those options to unmarshalling processors ( It's a regression so it needs to be fixed in next release. |
Agreed, thank you! We'd gotten as far as trying Similarly, we've previously disabled schema validation of our API responses for our |
I plan to add this option but this will need to wait for other changes that are needed for unmarshalling process. |
Actual Behavior
Our application is upgrading from openapi-core v0.14.5 to v0.18.0. We previously specified a custom
wkt
formatter by settingself.request_validator
in our class that inherits fromFlaskOpenAPIView
, see https://github.com/ASFHyP3/hyp3/blob/develop/apps/api/src/hyp3_api/routes.py#L173It appears that
FlaskOpenAPIView
no longer usesself.request_validator
in it'sdispatch_request method
: https://github.com/python-openapi/openapi-core/blob/master/openapi_core/contrib/flask/views.py#L21Is there an alternate way to specify a custom formatter when using this integration pattern?
Expected Behavior
N/A
Steps to Reproduce
N/A
OpenAPI Core Version
0.18.0
OpenAPI Core Integration
flask
Affected Area(s)
No response
References
No response
Anything else we need to know?
No response
Would you like to implement a fix?
None
The text was updated successfully, but these errors were encountered: