You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Flask: non-JSON input mappers, send_json_resp mappers and empty bodies #40
Follow-ups from the review of the flask support (#39, PR for it): under framework='flask' (1) handle_raw_req, handle_binary_req and the form mapper read Bottle's request (request.body, request.files) and fail per request with a 500 whose text leaks the AttributeError; they should fail at build time or be ported; (2) a user output mapper made with @send_json_resp sets Bottle's response.content_type, so Flask answers text/html; (3) an empty or non-JSON body gives a 500 with werkzeug's text instead of a 400 InputError; (4) Bottle-only configs (plugins, enable_cors, publish_swagger, openapi_insecure) are refused for flask; supporting them (JWT plugin equivalent as a before_request hook, CORS) is the real work.
Activity
Flask: non-JSON input mappers, send_*_resp content types, 400 on bad …
thorwhalen commentedon Oct 13, 2026
Items 1-3 landed in #43; item 4 continues in #42.