Bart Koelman

I have the line `enable` in `Directory.Build.props`, so it applies to all projects. The `#nullable enable` in the next screenshot is grayed out, because it is redundant. Yet it doesn't...

I'll give you a tip: The _only_ way to solve this reliably for projects with nullable on/off across all target frameworks is to suppress all of the C# nullability warnings...

> I 've created a powershell script that removes all noise https://gist.github.com/petriashev/03e3e2ec739560bc457c41366867b55f @petriashev The script didn't work for me. I had to change the "conditional bullshit" line from: ``` $content...

Interestingly, the script is actually a **BUGFIX** because it emits `#nullable enable` at the top of the file. Doing so is the _only_ way to correctly activate nullable reference types...

Perhaps in the future, but not anytime soon. It would also be helpful to have an out-of-the-box default implicit handler for HTTP 500, if that's not in the OpenAPI document....

Can you elaborate on the performance impact? I would have thought reading the first few kb avoids that.

Well, I tried adding a 5XX response, but that's a complete disaster: ```json { "responses": { // .... "400": { "description": "The query string is invalid.", "content": { "application/vnd.api+json": {...

> > Can you elaborate on the performance impact? I would have thought reading the first few kb avoids that. > > The first few kbs is a very arbitrary...

> @bkoelman I agree that having to add an explicit 5XX for every operation is a pain and shouldn't be necessary. But also, if you don't then you can't provide...

> I think I can say with some confidence that having a "developer friendly" message is irrelevant. It's the least of our worries. Developer care about the type of the...