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

bug: stop using ErrorResponse as field name #14

Merged
merged 1 commit into from
Jul 9, 2019

Conversation

mvid
Copy link
Contributor

@mvid mvid commented Jul 8, 2019

ErrorResponse is the type, error is the field name

@mvid
Copy link
Contributor Author

mvid commented Jul 8, 2019

Ran the tests locally, and the tests pass (except for the ones that are also failing in master)

@mvid mvid requested a review from vasco-santos July 8, 2019 20:33
@mvid mvid changed the title stop using ErrorResponse as field name bug: stop using ErrorResponse as field name Jul 8, 2019
Copy link
Member

@vasco-santos vasco-santos left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM! Thanks @mvid

This is right, the property name should be error instead of ErrorResponse!

I tried this locally, and getPublicKey test for the dht is not working properly. I will skip it for now and open an issue fixing it in a new PR

@vasco-santos vasco-santos merged commit 0ff9eda into master Jul 9, 2019
@vasco-santos vasco-santos deleted the bug/error-response-field-name branch July 9, 2019 10:08
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.

2 participants