leptos_reactive_axum
| Crates.io | leptos_reactive_axum |
| lib.rs | leptos_reactive_axum |
| version | |
| source | src |
| created_at | 2024-06-15 09:49:18.763435 |
| updated_at | 2024-10-20 09:07:40.517852 |
| description | reactive context for axum handlers |
| homepage | |
| repository | https://github.com/davidon-top/leptos_reactive_axum.git |
| max_upload_size | |
| id | 1272705 |
| Cargo.toml error: | TOML parse error at line 18, column 1 | 18 | autolib = false | ^^^^^^^ unknown field `autolib`, expected one of `name`, `version`, `edition`, `authors`, `description`, `readme`, `license`, `repository`, `homepage`, `documentation`, `build`, `resolver`, `links`, `default-run`, `default_dash_run`, `rust-version`, `rust_dash_version`, `rust_version`, `license-file`, `license_dash_file`, `license_file`, `licenseFile`, `license_capital_file`, `forced-target`, `forced_dash_target`, `autobins`, `autotests`, `autoexamples`, `autobenches`, `publish`, `metadata`, `keywords`, `categories`, `exclude`, `include` |
| size | 0 |
(davidon-top)
documentation
https://docs.rs/leptos_reactive_axum
README
whoami
Library providing utilities for using leptos_reactive runtime inside axum handlers. Also automaticly uses provide_context to make the request Parts available inside any function called by the handler.
But why?
When using something like the rstml-component crate it is usefull to be able to extract anything from parts inside any component. For example inside nav bar extract the path to be able to highlight active route. Additionally you can create a middleware layer that can add to the context things like IsLoggedIn or other information about the request that is used within more then one function/component called by the handler.