Skip to content

refactor: intuitively handle current object context #17553

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

Closed
wants to merge 1 commit into from
Closed

refactor: intuitively handle current object context #17553

wants to merge 1 commit into from

Conversation

mithunsasidharan
Copy link
Contributor

@mithunsasidharan mithunsasidharan commented Dec 8, 2017

Refactored to intuitively handle current object context

Checklist
  • make -j4 test (UNIX), or vcbuild test (Windows) passes
  • tests and/or benchmarks are included
  • commit message follows commit guidelines
Affected core subsystem(s)

test

@nodejs-github-bot nodejs-github-bot added the test Issues and PRs related to the tests. label Dec 8, 2017
@maclover7
Copy link
Contributor

Can you please update the commit message to follow the commit guidelines

@mithunsasidharan
Copy link
Contributor Author

@maclover7 : Thanks for the feedback. I'm not quite sure what you were referring to exactly in commit message that needs to be updated. Kindly advice. Thanks.

@apapirovski
Copy link
Contributor

@mithunsasidharan The commit messages should start with the subsystem being worked on, so in this case "test". See the link above.

@mithunsasidharan
Copy link
Contributor Author

@apapirovski : Thanks for pointing that out. I've updated the commit message. I hope the PR can be left the same. Kindly advice.

@maclover7
Copy link
Contributor

@mithunsasidharan mithunsasidharan changed the title refactor: intuitive handling of current object context refactor: intuitively handle current object context Dec 9, 2017
@maclover7 maclover7 added the author ready PRs that have at least one approval, no pending requests for changes, and a CI started. label Dec 11, 2017
@maclover7
Copy link
Contributor

Landing...

@maclover7 maclover7 self-assigned this Dec 11, 2017
@maclover7
Copy link
Contributor

Thank you for your contribution, landed in f3aaaa5.
❤️ 💚 💙 💛 💜

@maclover7 maclover7 closed this Dec 11, 2017
maclover7 pushed a commit to maclover7/node that referenced this pull request Dec 11, 2017
PR-URL: nodejs#17553
Reviewed-By: Jon Moss <me@jonathanmoss.me>
Reviewed-By: Luigi Pinca <luigipinca@gmail.com>
@mithunsasidharan mithunsasidharan deleted the pr_self branch December 12, 2017 01:03
MylesBorins pushed a commit that referenced this pull request Dec 12, 2017
PR-URL: #17553
Reviewed-By: Jon Moss <me@jonathanmoss.me>
Reviewed-By: Luigi Pinca <luigipinca@gmail.com>
MylesBorins pushed a commit that referenced this pull request Dec 12, 2017
PR-URL: #17553
Reviewed-By: Jon Moss <me@jonathanmoss.me>
Reviewed-By: Luigi Pinca <luigipinca@gmail.com>
@MylesBorins MylesBorins mentioned this pull request Dec 12, 2017
@addaleax addaleax removed the author ready PRs that have at least one approval, no pending requests for changes, and a CI started. label Dec 13, 2017
gibfahn pushed a commit that referenced this pull request Dec 20, 2017
PR-URL: #17553
Reviewed-By: Jon Moss <me@jonathanmoss.me>
Reviewed-By: Luigi Pinca <luigipinca@gmail.com>
@gibfahn gibfahn mentioned this pull request Dec 20, 2017
gibfahn pushed a commit that referenced this pull request Dec 20, 2017
PR-URL: #17553
Reviewed-By: Jon Moss <me@jonathanmoss.me>
Reviewed-By: Luigi Pinca <luigipinca@gmail.com>
@gibfahn gibfahn mentioned this pull request Dec 20, 2017
gibfahn pushed a commit that referenced this pull request Dec 20, 2017
PR-URL: #17553
Reviewed-By: Jon Moss <me@jonathanmoss.me>
Reviewed-By: Luigi Pinca <luigipinca@gmail.com>
# for free to join this conversation on GitHub. Already have an account? # to comment
Labels
test Issues and PRs related to the tests.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

7 participants