Skip to content

Conversation

@andrew-coleman
Copy link
Member

The fix for #247 introduced a significant performance regression.
This PR rewrites that bit of code to recover the loss.

@coveralls
Copy link

Coverage Status

Coverage remained the same at 100.0% when pulling af4fccd on faster into 64baffe on master.

3 similar comments
@coveralls
Copy link

Coverage Status

Coverage remained the same at 100.0% when pulling af4fccd on faster into 64baffe on master.

@coveralls
Copy link

Coverage Status

Coverage remained the same at 100.0% when pulling af4fccd on faster into 64baffe on master.

@coveralls
Copy link

Coverage Status

Coverage remained the same at 100.0% when pulling af4fccd on faster into 64baffe on master.

describe("$now() returns timestamp with defined format", function() {
it("should return result object", function() {
var expr = jsonata("$now('[h]:[M][P] [z]')");
var expr = jsonata("$now('[h]:[M01][P] [z]')");
Copy link
Member

Choose a reason for hiding this comment

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

I believe this is unrelated to the rest of the fixes, but agree with the change so not too worried that it's here.

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.

4 participants