Skip to content
Merged
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
8 changes: 1 addition & 7 deletions README.md
Original file line number Diff line number Diff line change
Expand Up @@ -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

Expand Down Expand Up @@ -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:
Expand Down
Loading