Skip to content
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

400 Bad Request errors do not show enough information to be useful #147

Open
jasonwbarnett opened this issue Oct 1, 2020 · 0 comments
Open
Labels
Status: Untriaged An issue that has yet to be triaged.

Comments

@jasonwbarnett
Copy link
Contributor

jasonwbarnett commented Oct 1, 2020

Describe the Enhancement:

Today the sum of errors is printed out at the end of a restore. If the error is a Net::HTTPServerException there is essentially no useful information.

The literal thing I was running into was users failing to be created because of a bad email address ex.response.body #=> {"error":["email must be valid"]}. This wasn't observable with the current information being logged.

Describe the Need:

Anybody who would like to correct an issue would want to know more details about the error so the issue can be corrected.

Current Alternative

Not that I can think of other than something like pry.

Can We Help You Implement This?:

Would like some direction in terms of best way to implement. I could see creating a custom exception class for these errors and then nesting the original exception in it. Then inside the EcErrorHandler add additional ways to format the output.

@jasonwbarnett jasonwbarnett added the Status: Untriaged An issue that has yet to be triaged. label Oct 1, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Status: Untriaged An issue that has yet to be triaged.
Projects
None yet
Development

No branches or pull requests

1 participant