hyperoute-macro 0.0.5
“Route / filter / WebSocket attribute macros (#[GET], #[FILTER], #[WEBSOCKET], ...) for hyperoute.”
Basename is uppercase README.mdNear-zero recent downloads for registry package
SHA-256dd3ef31c1a8800884d726b31b7467213b1ed229515aff59cae5e57f6575a51e8
MaleculeMd₂(Pt)
Evidence
1# hyperoute
2
3[English](README.md) | [简体中文](README.zh-CN.md)
4
5**Annotation-driven routing for [hyper](https://hyper.rs), generated at build time.**
6
7Write handlers the way you would in Spring MVC: put `#[GET("/users/{id}")]` on an `async fn`, and hyperoute takes care of routing, parameter extraction and response building. A `build.rs` step …
17:24… elopment (`0.0.x`). The API may still change between releases.
18
19## Features
20
21- **Route attributes**: `#[GET]`, `#[POST]`, `#[PUT]`, `#[DELETE]`, `#[PATCH]`, `#[HEAD]`, `#[OPTIONS]`, `#[CONNECT]`, `#[TRAC …
23:13… s by return type**: plain text, JSON, raw bytes with custom headers, streaming bodies, and `Result<T, E>`.
24- **Parameter errors that never panic**: a malformed parameter returns `400` with a message saying which parameter failed …
165:129… page_size`). How each kind of parameter handles this:
166
167| Parameter | How names are matched |
168|---|---|
169| JSON / urlencoded body, `Query<T>`, JSON re …
363:74… nce the headers are ready, while the body is still being sent.
364
365## WebSocket
366
367```rust
⋯4 lines
No evidence locations were recorded for this file. Raw result