Skip to content
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

chore: replace all vars with const #5875

Closed
wants to merge 1 commit into from

Conversation

SomeKittens
Copy link

Pull Request check-list

Please make sure to review and check all of these items:

  • Does make -j8 test (UNIX) or vcbuild test nosign (Windows) pass with
    this change (including linting)?
  • Is the commit message formatted according to [CONTRIBUTING.md][0]?
  • (N/A) If this change fixes a bug (or a performance problem), is a regression
    test (or a benchmark) included?
  • (N/A) Is a documentation update included (if this change modifies
    existing APIs, or introduces new ones)?

Description of change

A quick find and replace requested by @benjamingr

Tests were not performed, will be CI'd as mentioned here

A quick find and replace requested by @benjamingr
@MylesBorins
Copy link
Member

in the past we have opted to not do project wide churn like this. Personally -1.

@Fishrock123
Copy link
Member

Sorry, but we won't be doing this. This would create conflicts on literally every backport.

@benjamingr
Copy link
Member

I'd rather have several small PRs so it would be easier to review.

I asked for small changes, 58 files is really hard to review and as @thealphanerd stated it's something that's not typically done at Node.

@jasnell
Copy link
Member

jasnell commented Mar 23, 2016

Agree with the others, this needs to be done in smaller chunks.

var self = this;
var handled = false;
const self = this;
const handled = false;

Choose a reason for hiding this comment

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

This value is possibly modified, const will throw an error.

Copy link
Member

Choose a reason for hiding this comment

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

This is one of the reasons smaller PRs are preferable.

@cjihrig
Copy link
Contributor

cjihrig commented Mar 23, 2016

Sorry. Going to close this.

@cjihrig cjihrig closed this Mar 23, 2016
@MylesBorins
Copy link
Member

@SomeKittens fwiw thank you for making the PR! If you are looking for other ways to contribute please come hangout in #node-dev and we can find other places where you can help out!

@SomeKittens
Copy link
Author

Yup, sorry, misunderstanding between @benjamingr and I. Carry on!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

7 participants