Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Currently, if the frontend passes an invalid user id (which sometimes happens in production), the backend will return a 500 error. This patches this problem, catching the error and returning it as a 400. I also have an rspec test that checks this.
This pull request does a number of things:
Rspec does come back clean. And the app seems to work fine.
This fixes the server side problem of getguesstimate/guesstimate-app#1011. I'll see if I can hunt down the client side problem (why the client is sending invalid user ids in the first place)