Skip to content

src: elevate v8 namespaces of repeated artifacts - #24427

Merged
refack merged 1 commit into
nodejs:masterfrom
Shubhamurkade:namespace_change
Nov 18, 2018
Merged

src: elevate v8 namespaces of repeated artifacts#24427
refack merged 1 commit into
nodejs:masterfrom
Shubhamurkade:namespace_change

Conversation

@Shubhamurkade

Copy link
Copy Markdown
Contributor

There are several places where v8 artifacts appear with scope resolution operator inline with the source. Elevated the places where the same artifacts were used repeatedly. The places where an artifact was used only once has been retained as it is.

@nodejs-github-botnodejs-github-bot added c++ Issues and PRs that require attention from people who are familiar with C++. inspector Issues and PRs related to the V8 inspector protocol labels Nov 17, 2018
@gireeshpunathilgireeshpunathil added the code-and-learn Issues related to the Code-and-Learn events and PRs submitted during the events. label Nov 17, 2018
@targostargos added the fast-track PRs that do not need to wait for 48 hours to land. label Nov 17, 2018
@targos

Copy link
Copy Markdown
Member

👍 to fast-track

@targos

Copy link
Copy Markdown
Member

The first line of the commit message should be shorter (<=50 characters if possible)

@ShubhamurkadeShubhamurkade changed the title src: Elevate v8 namespaces of repeatedly referenced artifacts with 'using' keyword in src/inspector_agent.ccsrc: elevate v8 namespaces of repeated artifactsNov 17, 2018
@Shubhamurkade

Copy link
Copy Markdown
ContributorAuthor

The first line of the commit message should be shorter (<=50 characters if possible)

Does it look good now?

@refack

refack commented Nov 17, 2018

Copy link
Copy Markdown
Contributor

@refack

refack commented Nov 17, 2018

Copy link
Copy Markdown
Contributor

Hello @Shubhamurkade and welcome, and thank you for your contribution 🥇
If you are not familiar with our review and landing process, it's covered in CONTRIBUTING.md

P.S. If you have any questions you can also feel free to contact me directly.

@refack

refack commented Nov 17, 2018

Copy link
Copy Markdown
Contributor

FYI: @Shubhamurkade if you'd like you can associate your email with your GitHub account. That way we and GitHub will credit the code contributions you make to you. See https://github.com/settings/emails and the guide at https://help.github.com/articles/setting-your-commit-email-address-on-github/

@refackrefack added the blocked PRs that are blocked by other issues or PRs. label Nov 17, 2018
@Shubhamurkade

Copy link
Copy Markdown
ContributorAuthor

FYI: @Shubhamurkade if you'd like you can associate your email with your GitHub account. That way we and GitHub will credit the code contributions you make to you. See https://github.com/settings/emails and the guide at https://help.github.com/articles/setting-your-commit-email-address-on-github/

Hi @refack! I already have an email address associated with my github account. Please look at the attached image.
email

@refack

refack commented Nov 18, 2018

Copy link
Copy Markdown
Contributor

@Shubhamurkade it seems like that's not the email you have setup in your local git. You can see the GitHub doesn't recognize it in this screen 787db0f
image.
and in the header of git commit metadata - https://patch-diff.githubusercontent.com/raw/nodejs/node/pull/24427.patch

I'll try to fix it for this PR while landing it. ✔️

@refackrefack removed the blocked PRs that are blocked by other issues or PRs. label Nov 18, 2018
PR-URL: nodejs#24427
Reviewed-By: Michaël Zasso <targos@protonmail.com>
Reviewed-By: Refael Ackermann <refack@gmail.com>
Reviewed-By: Anna Henningsen <anna@addaleax.net>
Reviewed-By: Colin Ihrig <cjihrig@gmail.com>
Reviewed-By: Gireesh Punathil <gpunathi@in.ibm.com>
@refack
refack merged commit ea65519 into nodejs:masterNov 18, 2018
@refack

Copy link
Copy Markdown
Contributor

@Shubhamurkade congratulations 🎉 on getting promoted by GitHub form:
image
to
image

Hope to see you contributing again in the future!

@Trott

Copy link
Copy Markdown
Member

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/.)

@Shubhamurkade

Copy link
Copy Markdown
ContributorAuthor

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/.)

Thank you!

targos pushed a commit that referenced this pull request Nov 19, 2018
PR-URL: #24427
Reviewed-By: Michaël Zasso <targos@protonmail.com>
Reviewed-By: Refael Ackermann <refack@gmail.com>
Reviewed-By: Anna Henningsen <anna@addaleax.net>
Reviewed-By: Colin Ihrig <cjihrig@gmail.com>
Reviewed-By: Gireesh Punathil <gpunathi@in.ibm.com>
rvagg pushed a commit that referenced this pull request Nov 28, 2018
PR-URL: #24427
Reviewed-By: Michaël Zasso <targos@protonmail.com>
Reviewed-By: Refael Ackermann <refack@gmail.com>
Reviewed-By: Anna Henningsen <anna@addaleax.net>
Reviewed-By: Colin Ihrig <cjihrig@gmail.com>
Reviewed-By: Gireesh Punathil <gpunathi@in.ibm.com>
@BridgeARBridgeAR mentioned this pull request Dec 5, 2018
4 tasks
codebytere pushed a commit that referenced this pull request Jan 13, 2019
PR-URL: #24427
Reviewed-By: Michaël Zasso <targos@protonmail.com>
Reviewed-By: Refael Ackermann <refack@gmail.com>
Reviewed-By: Anna Henningsen <anna@addaleax.net>
Reviewed-By: Colin Ihrig <cjihrig@gmail.com>
Reviewed-By: Gireesh Punathil <gpunathi@in.ibm.com>
refack pushed a commit to refack/node that referenced this pull request Jan 14, 2019
PR-URL: nodejs#24427
Reviewed-By: Michaël Zasso <targos@protonmail.com>
Reviewed-By: Refael Ackermann <refack@gmail.com>
Reviewed-By: Anna Henningsen <anna@addaleax.net>
Reviewed-By: Colin Ihrig <cjihrig@gmail.com>
Reviewed-By: Gireesh Punathil <gpunathi@in.ibm.com>
@codebyterecodebytere mentioned this pull request Jan 15, 2019
codebytere pushed a commit that referenced this pull request Jan 29, 2019
PR-URL: #24427
Reviewed-By: Michaël Zasso <targos@protonmail.com>
Reviewed-By: Refael Ackermann <refack@gmail.com>
Reviewed-By: Anna Henningsen <anna@addaleax.net>
Reviewed-By: Colin Ihrig <cjihrig@gmail.com>
Reviewed-By: Gireesh Punathil <gpunathi@in.ibm.com>
Sign up for freeto join this conversation on GitHub. Already have an account? Sign in to comment

Labels

c++Issues and PRs that require attention from people who are familiar with C++.code-and-learnIssues related to the Code-and-Learn events and PRs submitted during the events.fast-trackPRs that do not need to wait for 48 hours to land.inspectorIssues and PRs related to the V8 inspector protocol

Projects

None yet

Development

Successfully merging this pull request may close these issues.

8 participants

@Shubhamurkade@targos@refack@Trott@addaleax@cjihrig@gireeshpunathil@nodejs-github-bot