| FazBrowse GitHub Viewer | Trending | | Home |
| Tools: [Download Repo ZIP] [Original HTTPS Page] |
Sorry, something went wrong.
There was a problem hiding this comment.
LGTM, but there is some other cleanup that you could do while you're here. Like getting rid of assert.equal() and assert.notEqual().
Sorry, something went wrong.
These changes would make this change more compelling:
|
Sorry, something went wrong.
|
@Goyapa while you are at it can you please replace assert.equal() with assert.strictEqual() and assert.notEqual() with assert.notStrictEqual(). Also you can use the Fixes: metadata instead of This commit resolves #8925 as defined in CONTRIBUTING.md. |
Sorry, something went wrong.
|
@ipinca |
Sorry, something went wrong.
|
@Goyapa we can use https://help.github.com/articles/allowing-changes-to-a-pull-request-branch-created-from-a-fork/ if it is not a problem for you. |
Sorry, something went wrong.
|
You can also try to edit files on your branch using Github’s web interface, it’s a bit tricky but it’s nice when you don’t want to or can’t use a local git client. |
Sorry, something went wrong.
|
@lpinca |
Sorry, something went wrong.
|
@lpinca |
Sorry, something went wrong.
* Changes: * var -> const * assert.equal() -> assert.strictEqual() * assert.notEqual() -> assert.notStrictEqual() * Fixes: #8925
Sorry, something went wrong.
| Back | FazBrowse Home | New Git URL |
Checklist
Affected core subsystem(s)
test
dgram
Description of change
test: cleanup/update test-dgram-error-message-address.js