Skip to content

Update dependencies. Update codebase to ES6/Node4#51

Closed
escalant3 wants to merge 3 commits intohapijs:masterfrom
escalant3:es6-and-node4
Closed

Update dependencies. Update codebase to ES6/Node4#51
escalant3 wants to merge 3 commits intohapijs:masterfrom
escalant3:es6-and-node4

Conversation

@escalant3
Copy link
Copy Markdown
Contributor

I have been exploring the Hapi codebase recently and I noticed inert was not ES6 ready. This PR should comply with all the requirements specified in #49

The linter was complaining about lots of things that were fixed:

  • No double assignments in loops.
  • Array functions everywhere (except a test that access arguments, too bad the rest operator is not available).
  • use strict and const always that it's possible.let only in mutable cases
  • package.json dependencies matching those in hapi/package.json
  • else should not be in the same line where the previous if closes
  • All tests passing. Test coverage 100%

Questions:

  • I guess that bumping to node 4.x is a breaking change so the version should be 4.0.0. But I am not sure how the Hapi team deals with versions.
  • I didn't change the +=. I could do it if needed.

Thanks for such an awesome framework. I hope this helps.

Cheers!

lib/directory.js Outdated
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

We're also not memoizing the length anymore unless necessary.

@kanongil kanongil modified the milestone: 4.0.0 Dec 22, 2015
@kanongil kanongil added the feature New functionality or improvement label Dec 22, 2015
@kanongil kanongil self-assigned this Dec 22, 2015
@kanongil
Copy link
Copy Markdown
Contributor

Thanks – merged in cbab9fc.

@kanongil kanongil closed this Dec 22, 2015
@kanongil kanongil added the breaking changes Change that can breaking existing code label Dec 23, 2015
@lock
Copy link
Copy Markdown

lock bot commented Jan 9, 2020

This thread has been automatically locked due to inactivity. Please open a new issue for related bugs or questions following the new issue template instructions.

@lock lock bot locked as resolved and limited conversation to collaborators Jan 9, 2020
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Labels

breaking changes Change that can breaking existing code feature New functionality or improvement

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants