-
Notifications
You must be signed in to change notification settings - Fork 234
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
refactor: eliminate need for error wrapper class #100
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.
I'm not able to properly review TS-only pull requests, so I'm more than happy with more deletions than additions :D
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.
Very nice :)
return createWrapper(null, result[0]) | ||
} | ||
|
||
return createWrapperError('VueWrapper') |
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.
I see we lost the selector on the error wrapper. What was it used for?
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.
Turns out it wasn't used for anything - maybe it was previously, but in the current master is it not used. So I just deleted it.
I'm late to the party, but I think this API is much more sound 👌 |
Greatly simplify the concept of
ErrorWrapper
and eliminate the need for theWrapperAPI
interfaces (since they are not implemented by more than one class).It's everyone favorite kind of PR - one that has more deletions than insertions!
#91 and #92