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

[[FEAT]] Make node 6 compatible #39

Merged
merged 5 commits into from
May 3, 2017
Merged

[[FEAT]] Make node 6 compatible #39

merged 5 commits into from
May 3, 2017

Conversation

jmendiara
Copy link
Member

Related #36

@jmendiara jmendiara mentioned this pull request May 1, 2017
6 tasks
@coveralls
Copy link

Coverage Status

Coverage remained the same at 100.0% when pulling a2db9aa on v2/moveToNode6 into 25f91ec on master.

1 similar comment
@coveralls
Copy link

Coverage Status

Coverage remained the same at 100.0% when pulling a2db9aa on v2/moveToNode6 into 25f91ec on master.

@@ -86,7 +86,7 @@ describe('Development format', function() {
it('should log dates', function() {
var now = new Date();
logger.info({}, now);
expect(logger._lastTrace).to.be.eql('INFO ' + now);
expect(logger._lastTrace).to.be.eql('INFO 1970-01-01T00:00:00.000Z');
Copy link
Member

Choose a reason for hiding this comment

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

Why 1970-01-01 and not the current date if you are logging a new Date?

Copy link
Member Author

Choose a reason for hiding this comment

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

Copy link
Member

@gtorodelvalle gtorodelvalle left a comment

Choose a reason for hiding this comment

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

LGTM on my side ;)

@jmendiara jmendiara merged commit 972fbe5 into master May 3, 2017
@jmendiara jmendiara deleted the v2/moveToNode6 branch May 3, 2017 18:25
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

4 participants