Expand description
The non-generated components of the Filigree web framework
Modules§
- Authentication and Authorization
- Helpers for parsing configuration
- Email templates and sending
- Interface to error reporting services
- Utilities for working with error_stack::Report
- Error handling
- Request extractors
- Utilities for genrating HTML
- htmx Utilities
- Extension trait to inspect the body of a Reqwest error response
- Utilities for working with Maud
- A UUIDv7-based type for handling object IDs with a more compact representation.
- Helpers to propagate HTTP spans to another server
- Common query string structures for use with Axum’s Query extractor
- Request Handling and Validation
- Services that can be placed in the Axum router
- Utilities for running an HTTP server
- Utilities for working with SQL queries
- Cloud object storage
- Template code generation helpers for the Filigree CLI
- Functionality to help test your app
- Tracing configuration
- Helpers to manage file uploads, for use with Storage::save_and_inspect_request_body.
- Manage users, roles, and related data
- Parse a Vite manifest and generate HTML to include each entrypoint.
Macros§
- Attempt to downcast_ref a error_stack::Frame into multiple error types, and map the first matching type through a function. The map function should be generic on some trait that the errors all implement, usually HttpError.
- Create a new ObjectId type. This automatically implements the prefix structure and creates a type alias for the type.
- Render a maud template lazily
Structs§
- A request body that only contains an email
- A simple structure for sending back a message-only response