Skip to content
New issue

Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? # to your account

assert: add compatibility for older Node.js versions #27672

Closed
wants to merge 1 commit into from

Conversation

BridgeAR
Copy link
Member

This makes sure the AssertionError still accepts the
stackStartFunction option as alternative to the stackStartFn.

Fixes: #27671

Checklist
  • make -j4 test (UNIX), or vcbuild test (Windows) passes
  • tests and/or benchmarks are included
  • documentation is changed or added
  • commit message follows commit guidelines

This makes sure the `AssertionError` still accepts the
`stackStartFunction` option as alternative to the `stackStartFn`.

Fixes: nodejs#27671
@nodejs-github-bot
Copy link
Collaborator

@nodejs-github-bot nodejs-github-bot added the assert Issues and PRs related to the assert subsystem. label May 13, 2019
@antsmartian antsmartian added the author ready PRs that have at least one approval, no pending requests for changes, and a CI started. label May 13, 2019
@nodejs-github-bot
Copy link
Collaborator

@Raynos
Copy link
Contributor

Raynos commented May 14, 2019

lgtm.

Copy link

@renanbastos93 renanbastos93 left a comment

Choose a reason for hiding this comment

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

LGTM, congrats on your job!

BridgeAR added a commit to BridgeAR/node that referenced this pull request May 16, 2019
This makes sure the `AssertionError` still accepts the
`stackStartFunction` option as alternative to the `stackStartFn`.

PR-URL: nodejs#27672
Fixes: nodejs#27671
Reviewed-By: Yongsheng Zhang <zyszys98@gmail.com>
Reviewed-By: Anto Aravinth <anto.aravinth.cse@gmail.com>
Reviewed-By: Anna Henningsen <anna@addaleax.net>
Reviewed-By: Rich Trott <rtrott@gmail.com>
Reviewed-By: Luigi Pinca <luigipinca@gmail.com>
Reviewed-By: Trivikram Kamat <trivikr.dev@gmail.com>
@BridgeAR
Copy link
Member Author

Landed in e632b1b 🎉

@BridgeAR BridgeAR closed this May 16, 2019
targos pushed a commit that referenced this pull request May 17, 2019
This makes sure the `AssertionError` still accepts the
`stackStartFunction` option as alternative to the `stackStartFn`.

PR-URL: #27672
Fixes: #27671
Reviewed-By: Yongsheng Zhang <zyszys98@gmail.com>
Reviewed-By: Anto Aravinth <anto.aravinth.cse@gmail.com>
Reviewed-By: Anna Henningsen <anna@addaleax.net>
Reviewed-By: Rich Trott <rtrott@gmail.com>
Reviewed-By: Luigi Pinca <luigipinca@gmail.com>
Reviewed-By: Trivikram Kamat <trivikr.dev@gmail.com>
@BridgeAR BridgeAR mentioned this pull request May 21, 2019
4 tasks
@BridgeAR BridgeAR deleted the assert-compatibility branch January 20, 2020 12:04
# for free to join this conversation on GitHub. Already have an account? # to comment
Labels
assert Issues and PRs related to the assert subsystem. author ready PRs that have at least one approval, no pending requests for changes, and a CI started.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Why did startStackFunction get renamed to startStackFn from 8.x to 10.x