| Commit message (Collapse) | Author | Age | |
|---|---|---|---|
| * | Handlers are _named operations_, which can be exposed via routes. | Owen Jacobson | 2025-06-18 |
| | | | | | | | Each domain module that exposes handlers does so through a `handlers` child module, ideally as a top-level symbol that can be plugged directly into Axum's `MethodRouter`. Modules could make exceptions to this - kill the doctrinaire inside yourself, after all - but none of the API modules that actually exist need such exceptions, and consistency is useful. The related details of request types, URL types, response types, errors, &c &c are then organized into modules under `handlers`, along with their respective tests. | ||
| * | Tests for purged channels and messages. | Owen Jacobson | 2024-10-25 |
| | | | | | This required a re-think of the `.immediately()` combinator, to generalize it to cases where a message is _not_ expected. That (more or less immediately) suggested some mixed combinators, particularly for stream futures (futures of `Option<T>`). | ||
| * | Sort out the naming of the various parts of an identity. | Owen Jacobson | 2024-10-22 |
| | | | | | | | | | | * A `cookie::Identity` (`IdentityCookie`) is a specialized CookieJar for working with identities. * An `Identity` is a token/login pair. I hope for this to be a bit more legible. In service of this, `Login` is no longer extractable. You have to get an identity. | ||
| * | Organizational pass on endpoints and routes. | Owen Jacobson | 2024-10-16 |
 |
index : pilcrow | |
| Run-It-Yourself web chat, maybe |
| summaryrefslogtreecommitdiff |