Pattern is the same. Although with DI this will fail before calling constructor.
What is the correct way to fail in a WebApi Controller constructor
-
10-03-2022 - |
Question
I have a WebApi Controller that requires a service via it's constructor. If this service is null I would usually throw a NullArguementException
. Is this still the correct way to fail in the context of a WebApi Controller or is there a different pattern for this.
Solution
Licensed under: CC-BY-SA with attribution
Not affiliated with StackOverflow