-
Notifications
You must be signed in to change notification settings - Fork 8
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
[MMB-44] Ensure we're setting proper error codes #135
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
The majority of errors we are throwing are default InvalidArgumentError type errors. Otherwise, we only really have two other errors: 1. Attempting to connect to a space where the name is missing 2. Trying to do something when they have entered a space I've copied the way that locks used errors.
Let's ensure we never have a throw that isn't at least a standard generic error code.
f397291
to
33bb373
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@surminus I've suggested some change in wording so it's more contextual. wdyt?
@Srushtika I went with OUT_OF_SPACE error as a reference to the Prodigy song, but I'm happy to do something more useful as suggested! 😉 |
@Srushtika updated! |
The majority of errors we are throwing are default InvalidArgumentError type errors.
Otherwise, we only really have two other errors:
I've copied the way that locks used errors.