Your REST API Errors Are Wrong. Problem Details Will Fix This

[@MilanJovanovicTech]

Want to master Clean Architecture? Go here: bit.ly/3PupkOJ Want to unlock Modular Monoliths? Go here: bit.ly/3SXlzSt

[@paulmdevenney]

dude - your timing is impeccable. I was just tidying up my version of the same thing. Took some notes, made some refinements. Thanks as always.

[@MilanJovanovicTech]

Nice, happy to help!

[@ghoulking715]

we are waiting for the continuation of the series about authorization via keycloak and setting up user roles and attributes 😊

[@MilanJovanovicTech]

Working on it

[@enricoroselino7557]

if girlfriend also have problem details, men doesnt need to think hard

[@MilanJovanovicTech]

You're screwed either way 😅

[@fakhrulhilal]

I've been using Seq for logging for years, but I never realize we can use it for telemetry. Nice video as always.

[@MilanJovanovicTech]

Tracing is a new feature

[@androidsavior]

Where request it and trace it are stored in the server ? Where are the logs

[@luisnataren4149]

Hey Milan, do you know when the REST API course will be ready?

[@MilanJovanovicTech]

January

[@10Totti]

Best tutorial! But Service ProblemDetails is add with .net 9 ?

[@MilanJovanovicTech]

No, it's there from way before

[@JuanOG]

How about using the hellang problem details package which seems to do this all well enough.

[@MilanJovanovicTech]

Prefer not to use 3rd party packages for simple things

[@sotsch9280]

How do you handle Results using the Result pattern? First naive thoughts would be simply using a middleware and checking for failed results?... I mainly use Results instead of throwing, except for Domain objects like ValueObjects, they throw if validation fails

[@MilanJovanovicTech]

if (Failure) - > return Result converted to Problem Details

[@sotsch9280]

@MilanJovanovicTech sorry, I meant not the mapping part, i meant how to handle that globally like with global exception handling. I thought you must have encountered this problem. Or am I missthinking this?

[@ivansusic562]

A kinda offtopic, but - I faced issue with postgres, ef migrations and docker compose - api was trying to do a migration on startup before postgres was ready. Do you have any suggestions here? Btw., great video. I just bought one of your courses - looking forward.

[@JollyGiant19]

Don’t run migrations on start up, run them outside the application. EF Core gives you a few ways to do that: script or binary.

[@MilanJovanovicTech]

Use "depends_on" to tell the API container to wait for the DB

[@ivansusic562]

@@MilanJovanovicTech I think I tried it - but it does not meen that postgres is ready if its container is up and running.

[@dinulilea4184]

Had the same issue with sqlx and postgres (rust project) where it tried to run queries at compile time before the posgres db was ready. Turns out there was an SQLX_OFFLINE env var that could be configured for docker compose. Maybe there is something similar with EF Cofe

[@Crisicus_01]

@@ivansusic562You can add health checks to see if the container is actually ready

[@MahbuburRahman-uc7np]

How are you showing inline values during debug in Visual Studio?

[@MilanJovanovicTech]

ReSharper

[@emanuelcordovamontiel1017]

Thank a lots, Milan!. Where can I found the source code of this solution?

[@MilanJovanovicTech]

Here: www.patreon.com/milanjovanovic

[@jeancarlosreyesencarnacion]

I know it's gonna be good. 🙌🙌

[@MilanJovanovicTech]

Was it?

[@jeancarlosreyesencarnacion]

@MilanJovanovicTech Yes, it was. 🤙

[@cuserroro]

I realy like!!

[@MilanJovanovicTech]

Thanks

[@lolyasuo1235]

How something that is fully opinionated can be wrong? Both approaches are just fine. I am sorry to say this, but I miss old era where developers were thinking about a solution. Today in many cases we are simply following guidelines (use ProblemDetails, use Result etc).

[@MilanJovanovicTech]

You didn't explain how it can be wrong

[@MahmoudSaed98]

❤

[@MilanJovanovicTech]

Much appreciated