-
Notifications
You must be signed in to change notification settings - Fork 13
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
Rename from environment
to context
#152
Conversation
assertEquals(isContextError(new ContextError('Yes')), true) | ||
assertEquals(isContextError(new EnvironmentError('Yes')), true) |
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.
These are important in this change
assertEquals(isEnvironmentError(new Error('No')), false) | ||
assertEquals(isEnvironmentError(new InputError('No')), false) | ||
assertEquals(isEnvironmentError(new ContextError('Yes')), true) |
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.
So are these 2 tests
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
Environment has always been a word which required some "context" (🥁) to be understood while
context
is arguably easier.This change won't be breaking because we are deprecating
EnvironmentError
andisEnvironmentError
and it can be easily replaced byContextError
andisContextError
.