@wiredprairie Oh! I’ve run into that issue as well! Not on Axum though. Where I encountered it the error messaging was a bit more clear although equally frustrating to debug. 😅

Glad you figured it out though!

@mike It’s accessibility for me in reverse. :/ I’m prone to migraines and high contrast / bright backgrounds trigger them much more frequently.

90% of sites I end up dealing with cater the opposite direction 🥲

@mike Yeah light modes are definitely an accessibility issue for some. Especially people with older eyes that don’t see as well.

If there is only 1 mode though I 100% prefer they start with dark. 😅

@wiredprairie I had issues with Appstate a while back. I wasn’t including the state on the route using with_state() properly. Not sure if this applies here. One thing that I see those is impl IntoResponse.

I had to replace that with Response and call into() on the return values. The issue with IntoResponse is it still only allows one type. Which can be fine if you only have 1 valid return but trickier if you need to return a redirect or something on a different case.

@nrc This is similar to my issue. I think that cloning should be considered expensive. It’s easy to reach for interim lifetime issues but, shouldn’t be default behavior.

If it is implemented I would like the ability derive it on specific types as opposed to having it as a default behavior for any.

@ThePinkHacker @nixCraft Careful or you’ll turn into a functional programmer. 😅

Iterations are really great though. They provide a lot more context and allow for more design patterns than for loops. They can make external mutable state a little tricker. But, Rust, for the most part pushes you away from that anyways.