-
Notifications
You must be signed in to change notification settings - Fork 143
Better error message for invalid changed hook name #216
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.
Comment about wording
Co-Authored-By: Paul Doyle <[email protected]>
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.
Whoops, looks like the line is too long now 😅
Can you fix this up manually and update the PR?
Other than that, I think this is fine. What do you think, @LPGhatguy ?
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!
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 as well
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.
Whoops, approved it as an old account that got logged in on my phone.
Closes #206
It seemed like an easy improvement. I made the error message as explicit as I could.
One thing I'd like to be double checked on, is that the protected call won't catch another error and put that message instead. The case I see that could be misleading is if
self._instance
is nil, but is that reasonably possible?Checklist before submitting:
CHANGELOG.md