Skip to content
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

Return response in the error #5

Merged
merged 1 commit into from
May 23, 2017
Merged

Conversation

maghis
Copy link
Contributor

@maghis maghis commented May 18, 2017

No description provided.

@coveralls
Copy link

coveralls commented May 18, 2017

Coverage Status

Coverage remained the same at 100.0% when pulling 4d2d364 on maghis:error-resp into 40a5ba4 on blakeembrey:master.

@blakeembrey
Copy link
Member

This makes sense, but it makes me wonder - is this better suited to generating errors on the response directly instead? Perhaps we want to abstract out the method for generating errors better in the future to accept both an optional request and response?

@maghis
Copy link
Contributor Author

maghis commented May 18, 2017

@blakeembrey probably it's better. I was also thinking that we could type the type the error and provide an isPopsicleError() type guard.

@blakeembrey blakeembrey merged commit 688022b into serviejs:master May 23, 2017
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

3 participants