Working currenlty with the maintainer of NSwag I get to hear always how hard it is considering all the edge cases for so many people and and not breaking things since so many people use it. I would doubt that MS would be open so much for thus customization but would rather just provide an opinionated way.
I don't get the hate for regions either. I've seen a few OSS projects use them and it makes reading through their code in an IDE really nice. E g. FusionCache
It's an artifact of the way operation transformers are implemented. It's effectively a correlation ID that allows us to map an OpenAPI operation to its matching ApIDescription instance. I actually just opened a PR to remove it from the final serialized document since it's not really meant to be stored in the final document (although it is helpful for debugging).
Fantastic! Thanks so much!
Ooh.. That "heck" distorts just enough that I needed to listen to it 3 times to make sure it wasn't a f-bomb 😁😁
Working currenlty with the maintainer of NSwag I get to hear always how hard it is considering all the edge cases for so many people and and not breaking things since so many people use it. I would doubt that MS would be open so much for thus customization but would rather just provide an opinionated way.
I don't get the hate for regions either. I've seen a few OSS projects use them and it makes reading through their code in an IDE really nice. E g. FusionCache
hey Jon, good afternoon, the Url in the comments doesnt match the one on the video! ~ thanks
You should find all correct links here: www.theurlist.com/aspnet-standup-2024-05-28
I just learned about mermaid from this, seems cool! Might use it to make some diagrams now.
What about SignalR Hubs documentation? It would be cool to use AsyncApi.
What's up with `x-aspnetcore-id` in the generated doc?
It's an artifact of the way operation transformers are implemented. It's effectively a correlation ID that allows us to map an OpenAPI operation to its matching ApIDescription instance. I actually just opened a PR to remove it from the final serialized document since it's not really meant to be stored in the final document (although it is helpful for debugging).
Is it too much to ask for a single solitary example of the "new stuff" in the context of a controller? I'm drowning in minimal api examples.
You should not expose swagger UI in productive environments. then you have no issues of leaking anything secret.