From a46aa7f28b236906b6cbd0feb20be33d8cfd21fe Mon Sep 17 00:00:00 2001 From: Sisyphus Date: Thu, 23 Jul 2026 14:13:49 +0900 Subject: [PATCH] docs: merge redundant Features list into What it does Closes #239 --- README.md | 8 +------- 1 file changed, 1 insertion(+), 7 deletions(-) diff --git a/README.md b/README.md index ddbfac9..e7d2139 100644 --- a/README.md +++ b/README.md @@ -37,6 +37,7 @@ Azure Functions Python v2 handlers often drift into the same repeated problems: - **Automatic error responses** — invalid requests get consistent `400`/`422` JSON error bodies - **Response model enforcement** — mismatches raise `ResponseValidationError` (HTTP 500) - **Decorator-first API** — `@validate_http` wraps your handler, no boilerplate needed +- **Custom error formatting** — per-handler error shaping via `ErrorFormatter` ## How it works @@ -203,13 +204,6 @@ This package does not own: - Runtime exposure or graph deployment — use [`azure-functions-langgraph`](https://github.com/yeongseon/azure-functions-langgraph-python) - Project scaffolding — use [`azure-functions-scaffold`](https://github.com/yeongseon/azure-functions-scaffold-python) -## Features - -- Typed body, query, path, and header validation via `@validate_http` -- Automatic 400 / 422 responses with `{"detail": [...]}` envelope -- Response model validation — mismatches raise `ResponseValidationError` (HTTP 500) -- Custom per-handler error formatting via `ErrorFormatter` - ## Package names Three names cover three different contexts: