Skip to content

Revert "Revert "console: use consolePropAttributes for k-bind propert… - #27352

Closed
BridgeAR wants to merge 1 commit into
nodejs:masterfrom
BridgeAR:revert-revert-console
Closed

Revert "Revert "console: use consolePropAttributes for k-bind propert…#27352
BridgeAR wants to merge 1 commit into
nodejs:masterfrom
BridgeAR:revert-revert-console

Conversation

@BridgeAR

@BridgeARBridgeAR commented Apr 23, 2019

Copy link
Copy Markdown
Member

…ies in constructor""

This reverts commit a8eac78.

The revert turned out not to be the actual cause of the test failure. Random changes caused the test to constantly fail.

Refs: #26401 (comment)

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

@nodejs-github-bot

Copy link
Copy Markdown
Collaborator

@nodejs-github-botnodejs-github-bot added the console Issues and PRs related to the console subsystem. label Apr 23, 2019
@nodejs-github-bot

This comment has been minimized.

@refackrefack added the author ready PRs that have at least one approval, no pending requests for changes, and a CI started. label Apr 23, 2019
@nodejs-github-bot

This comment has been minimized.

@nodejs-github-bot

nodejs-github-bot commented Apr 26, 2019

Copy link
Copy Markdown
Collaborator

@BridgeAR

Copy link
Copy Markdown
MemberAuthor

@nodejs/tsc I am not certain if I should stick to the commit message. We normally do that in case of an revert but in this case our subsystem validation complains about the commit message. Any suggestions?

@targos

Copy link
Copy Markdown
Member

I'd just keep the message of the original commit. And maybe add something like Reland of {original-pr-url}.

@BridgeAR

Copy link
Copy Markdown
MemberAuthor

Landed in 6bfde6a 🎉

BridgeAR added a commit to BridgeAR/node that referenced this pull request Apr 29, 2019
This is a reland of nodejs#26850.
It was speculatively reverted but it turned out that this did not
cause any trouble.
PR-URL: nodejs#27352
Refs: nodejs#26943
Refs: nodejs#26850
Reviewed-By: Daniel Bevenius <daniel.bevenius@gmail.com>
Reviewed-By: Refael Ackermann <refack@gmail.com>
Reviewed-By: Rich Trott <rtrott@gmail.com>
targos pushed a commit that referenced this pull request Apr 30, 2019
This is a reland of #26850.
It was speculatively reverted but it turned out that this did not
cause any trouble.
PR-URL: #27352
Refs: #26943
Refs: #26850
Reviewed-By: Daniel Bevenius <daniel.bevenius@gmail.com>
Reviewed-By: Refael Ackermann <refack@gmail.com>
Reviewed-By: Rich Trott <rtrott@gmail.com>
@targostargos mentioned this pull request May 6, 2019
@BridgeAR
BridgeAR deleted the revert-revert-console branch January 20, 2020 12:02
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.consoleIssues and PRs related to the console subsystem.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

6 participants

@BridgeAR@nodejs-github-bot@targos@refack@danbev@Trott