Dustin Moris Gorski

Thanks to both of you for sharing your code in order to add this feature. When I get around to implement it then I will get back to you if...

Hi, yes you should still be able to use that handler for an endpoint.

Hi, thanks for this suggestion. There could be value in exposing such extra handlers if they are generic enough. What are the typical checks that you can think of that...

What do the different health checks do? If you want different health checks then you can have multiple endpoints: /health >=> healthCheck /live >=> liveCheck /ready >=> readyCheck etc. If...

Hi, I think it is not needed, but because the authentication/authorization piece in ASP.NET Core is so fragmented it can be easily misunderstood so that one would like to have...

From your example it seems that `subRoute "/admin/7mPfJB" Admin.Dashboard.handler` is too greedy and swallows up the other routes too because it is a substring of those: ```fsharp subRoute "/admin/7mPfJBOVuxLpXCCSYO5Lf2Ro" Admin.Dashboard.handler...

@inputusernamehere What did you end up doing in the end? Is there something worth putting back into Giraffe or potentially PRing directly to `Utf8Json`?

I'd prefer to make the first parameter of each of these handlers to accept an error handler. It's not just about changing the message, but the entire response should be...

Hi, this is not intended, so must be a bug. I'll have a look later tonight!

Can you show me how you configured your custom serializer?