Uh oh!
There was an error while loading. Please reload this page.
- Notifications
You must be signed in to change notification settings - Fork 34.4k
test: fix strictEqual argument order#24153
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
Closed
KaskMartin wants to merge 1 commit into nodejs:master from KaskMartin:fix-test-buffer-slice-assert-argument-order
Closed
test: fix strictEqual argument order #24153
KaskMartin wants to merge 1 commit into nodejs:master from KaskMartin:fix-test-buffer-slice-assert-argument-order
Uh oh!
There was an error while loading. Please reload this page.
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters. Learn more about bidirectional Unicode characters
BridgeAR approved these changes Nov 6, 2018
cjihrig approved these changes Nov 6, 2018
gireeshpunathil approved these changes Nov 6, 2018
trivikr approved these changes Nov 7, 2018
Member
gireeshpunathil commented Nov 9, 2018
Uh oh!
There was an error while loading. Please reload this page.
e2e7046 to 414c953CompareFix the order of assert.strictEqual() arguments. It should have first argument as the calculated/tested value.
414c953 to ad527cdComparejasnell approved these changes Nov 10, 2018
Member
Trott commented Nov 11, 2018
Member
Trott commented Nov 12, 2018
Landed in 8efad19. Thanks for the contribution! 🎉 (If you're interested in other possible contributions to Node.js but don't have a good idea of where to start looking, some ideas are posted at https://www.nodetodo.org/next-steps/.) |
Trott pushed a commit to Trott/io.js that referenced this pull request Nov 12, 2018
Fix the order of assert.strictEqual() arguments. It should have first argument as the calculated/tested value. PR-URL: nodejs#24153 Reviewed-By: Ruben Bridgewater <[email protected]> Reviewed-By: Colin Ihrig <[email protected]> Reviewed-By: Gireesh Punathil <[email protected]> Reviewed-By: Trivikram Kamat <[email protected]> Reviewed-By: James M Snell <[email protected]>
BridgeAR pushed a commit that referenced this pull request Nov 14, 2018
Fix the order of assert.strictEqual() arguments. It should have first argument as the calculated/tested value. PR-URL: #24153 Reviewed-By: Ruben Bridgewater <[email protected]> Reviewed-By: Colin Ihrig <[email protected]> Reviewed-By: Gireesh Punathil <[email protected]> Reviewed-By: Trivikram Kamat <[email protected]> Reviewed-By: James M Snell <[email protected]>
kiyomizumia pushed a commit to kiyomizumia/node that referenced this pull request Nov 15, 2018
Fix the order of assert.strictEqual() arguments. It should have first argument as the calculated/tested value. PR-URL: nodejs#24153 Reviewed-By: Ruben Bridgewater <[email protected]> Reviewed-By: Colin Ihrig <[email protected]> Reviewed-By: Gireesh Punathil <[email protected]> Reviewed-By: Trivikram Kamat <[email protected]> Reviewed-By: James M Snell <[email protected]>
This was referenced Nov 15, 2018
codebytere pushed a commit that referenced this pull request Dec 14, 2018
Fix the order of assert.strictEqual() arguments. It should have first argument as the calculated/tested value. PR-URL: #24153 Reviewed-By: Ruben Bridgewater <[email protected]> Reviewed-By: Colin Ihrig <[email protected]> Reviewed-By: Gireesh Punathil <[email protected]> Reviewed-By: Trivikram Kamat <[email protected]> Reviewed-By: James M Snell <[email protected]>
MylesBorins pushed a commit that referenced this pull request Dec 26, 2018
Fix the order of assert.strictEqual() arguments. It should have first argument as the calculated/tested value. PR-URL: #24153 Reviewed-By: Ruben Bridgewater <[email protected]> Reviewed-By: Colin Ihrig <[email protected]> Reviewed-By: Gireesh Punathil <[email protected]> Reviewed-By: Trivikram Kamat <[email protected]> Reviewed-By: James M Snell <[email protected]>
Merged
This was referenced Jan 29, 2019
Sign up for freeto join this conversation on GitHub. Already have an account? Sign in to comment
Labels
author readyPRs that have at least one approval, no pending requests for changes, and a CI started. code-and-learnIssues related to the Code-and-Learn events and PRs submitted during the events. testIssues and PRs related to the tests.
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Fix the order of assert.strictEqual() arguments.
It should have first argument as the calculated/tested value