João Antunes<p>Kind of sad that the linked issue, about being able to tailor a nice 400 response with actionable information for the API client, doesn't seem to even come close to be a priority.</p><p>Does nobody care about providing information about what went wrong when handling an API request? I'd think this should be a must from the get go, but given its complete absence from the framework and lack of folks asking for it, maybe I'm the minority here.</p><p><a href="https://mastodon.social/tags/DotNet" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>DotNet</span></a> <a href="https://mastodon.social/tags/CSharp" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>CSharp</span></a> <a href="https://mastodon.social/tags/MinimalApis" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>MinimalApis</span></a></p><p><a href="https://github.com/dotnet/aspnetcore/issues/57337" rel="nofollow noopener" translate="no" target="_blank"><span class="invisible">https://</span><span class="ellipsis">github.com/dotnet/aspnetcore/i</span><span class="invisible">ssues/57337</span></a></p>