-
Notifications
You must be signed in to change notification settings - Fork 8.2k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Remove Boom errors for non API related files #49822
Comments
Pinging @elastic/kibana-stack-services (Team:Stack Services) |
This shouldn't be too bad. Across actions and alerting, there are only 5 files using Boom and 6 usages of it total, and they are all |
@mikecote Does this need to be done by 8.0? |
@ymao1 not for 8.0 based on what I recall. This was regarding migrating to the Kibana Platform, which we did a while ago. Now it just seems bad practice to use Boom errors, I believe. |
This would mean to catch errors at the API level and convert to proper status code. This is required for new platform and NP best practices.
The text was updated successfully, but these errors were encountered: