# axum-htmx
crates.io badge docs.rs badge

`axum-htmx` is a small extension library providing extractors and request guards for the various [htmx](https://htmx.org/) headers within [axum](https://github.com/tokio-rs/axum). Additionally, the library exports const values for all of the htmx headers, so there's no need to mess with strings in your handlers. ## Getting Started Simply run `cargo add axum-htmx` to add the library to your project. If you are using the unreleased branch of `axum` from GitHub, you can build against the `main` version of `axum-htmx` by adding the following to your `Cargo.toml`: ```toml [dependencies] axum-htmx = { git = "https://github.com/robertwayne/axum-htmx" } ``` ## Extractors All of the [htmx request headers](https://htmx.org/reference/#request_headers) have a supported extractor. Additionally, all extractors are infallible, meaning they will always succeed and never return an error. If the header is not present, the extractor will return `None` or `false` in most cases. | Header | Extractor | Value | |------------------------------|---------------------------|------------------| | `HX-Boosted` | `HxBoosted` | `bool` | | `HX-Current-URL` | `HxCurrentUrl` | `Option` | | `HX-History-Restore-Request` | `HxHistoryRestoreRequest` | `bool` | | `HX-Prompt` | `HxPrompt` | `Option` | | `HX-Request` | `HxRequest` | `bool` | | `HX-Target` | `HxTarget` | `Option` | | `HX-Trigger-Name` | `HxTriggerName` | `Option` | | `HX-Trigger` | `HxTrigger` | `Option` | ## Request Guards __Requires features `guards`.__ In addition to the extractors, there is also a route-wide layer request guard for the `HX-Request` header. This will redirect any requests without the header to "/" by default. _It should be noted that this is NOT a replacement for an auth guard. A user can trivially set the `HX-Request` header themselves. This is merely a convenience for preventing users from receiving partial responses without context. If you need to secure an endpoint you should be using a proper auth system._ ## Example: Extractors In this example, we'll look for the `HX-Boosted` header, which is set when applying the [hx-boost](https://htmx.org/attributes/hx-boost/) attribute to an element. In our case, we'll use it to determine what kind of response we send. When is this useful? When using a templating engine, like [minijinja](https://github.com/mitsuhiko/minijinja), it is common to extend different templates from a `_base.html` template. However, htmx works by sending partial responses, so extending our `_base.html` would result in lots of extra data being sent over the wire. If we wanted to swap between pages, we would need to support both full template responses and partial responses _(as the page can be accessed directly or through a boosted anchor)_, so we look for the `HX-Boosted` header and extend from a `_partial.html` template instead. ```rust use axum::response::IntoResponse; use axum_htmx::HxBoosted; async fn get_index(HxBoosted(boosted): HxBoosted) -> impl IntoResponse { if boosted { // Send a template extending from _partial.html } else { // Send a template extending from _base.html } } ``` ### Example: Router Guard ```rust use axum::Router; use axum_htmx::HxRequestGuardLayer; fn protected_router() -> Router { Router::new() .layer(HxRequestGuardLayer::default()) } ``` ### Feature Flags | Flag | Default | Description | Dependencies | |----------|----------|----------------------------|---------------------------------------------| | `guards` | Disabled | Adds request guard layers. | `tower`, `futures-core`, `pin-project-lite` | ## Contributing Contributions are always welcome! If you have an idea for a feature or find a bug, let me know. PR's are appreciated, but if it's not a small change, please open an issue first so we're all on the same page! ## License `axum-htmx` is dual-licensed under either - **[MIT License](/LICENSE-MIT)** - **[Apache License, Version 2.0](/LICENSE-APACHE)** at your option.