Sometimes it's not clear to developers that they can catch a validation exception to see the validation errors they're encountering. When this happens, they end up needing to contact us to figure out what the underlying problem is.
Solution
Added @throws tags for endpoints so IDEs are aware when there are unhandled exceptions
Added try/catch block to the creating Customers example
Added directions on how to expose validation errors in the exception message itself so it's more clear what to do when it's seen in logs or CLI output:
Problem
Sometimes it's not clear to developers that they can catch a validation exception to see the validation errors they're encountering. When this happens, they end up needing to contact us to figure out what the underlying problem is.
Solution
@throwstags for endpoints so IDEs are aware when there are unhandled exceptions