![Visual studio marketplace](https://kumkoniak.com/6.jpg)
![visual studio marketplace visual studio marketplace](https://docs.devexpress.com/CodeRushForRoslyn/images/getst_step3_2.png)
IMO validation on the input data only really needs to be strict enough that we don't have to manually implement guard conditions.Į.g: version: Joi.string().required() is there so we can write This allows us to make the validation declarative, centralise/DRY-up the rendering of error responses and log uncaught errors to sentry (which allows us to patch up the things we've missed over time). split() on it, we make sure its a string. If we need to multiply it by something, we check its a number. If we're going to use a value, we check it exists. Every API response we accept, we validate it against a schema to make sure its the right shape. This was better for users, but we were duplicating the same checks over and over, throwing the same error responses in hundreds of places, and we still missed stuff sometimes (we couldn't log error cases to sentry, for example - we just rendered broken badges). (except at that time we didn't have standard exceptions or a render() function, but.
![Visual studio marketplace](https://kumkoniak.com/6.jpg)