@HassanRezkHabib@HuntJason@cecilphillip@JohnGalt2727 We’ve being using aspnetcore Odata extensively in our backend services with Swagger, EFCore and Postgres without much issue. We even support custom fields via STJ JsonDocument. We’ve written a bit of shim code between most of these bits to deal with the rough edges.
@shanselman@davidfowl Agree. Also not a fan, just an awkward thing to type and read. I read it as "bang bang" when it should read "not null". Suggest !null like a few others have suggested would be better. Do we really need this at all?
There are days when you methodically diagnose and debug a problem and arrive at a solution that makes sense and we all learn from it, and then there's today where you just smash buttons in the #Azure portal until it works.
@davidfowl@robertmclaws An interface IUserContext that has some custom properties and exposes ClaimsPrincipal, implementations normally use IHttpContextAccesor when in aspnet
@variableirony@haacked A lot of it is dev/admin misconfigured apps, but just better error messages would be a start. That being said, useful errors for complex systems like identity federation are hard.
@haacked Agree. The success user flows are fine, but when something goes wrong, I can typically figure out whats wrong, but I don't know how normal people do.