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

proper error objects on callbacks #187

Merged
merged 1 commit into from
Aug 21, 2017
Merged

Conversation

julianduque
Copy link
Contributor

@julianduque julianduque commented Aug 18, 2017

It is a best practice to pass an error object to a callback instead of a string.

In this pull request I updated standard (to catch this errors in the future) and removed an unnecessary return statement (reported by standard).

package.json Outdated
@@ -21,12 +21,13 @@
"ethereumjs-blockchain": "^1.4.1",
"ethereumjs-testing": "https://github.com/ethereumjs/ethereumjs-testing",
"ethereumjs-tx": "1.3.3",
"install": "^0.10.1",
Copy link
Member

Choose a reason for hiding this comment

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

What is this used for?

Copy link
Contributor Author

Choose a reason for hiding this comment

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

A mistake, I removed it

@axic
Copy link
Member

axic commented Aug 18, 2017

Can you please split the linter change into a different PR?

@julianduque
Copy link
Contributor Author

@axic sure, let me split them

@julianduque julianduque changed the title proper error objects and update linter proper error objects on callbacks Aug 18, 2017
@axic axic merged commit c40eccb into ethereumjs:master Aug 21, 2017
@julianduque julianduque deleted the proper-errors branch August 21, 2017 14:19
evertonfraga added a commit to evertonfraga/ethereumjs-vm that referenced this pull request Dec 16, 2019
holgerd77 pushed a commit that referenced this pull request Dec 1, 2020
holgerd77 added a commit that referenced this pull request Mar 11, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants