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

Update jsonata to 1.6.5 which should fix #2183 #2224

Merged
merged 2 commits into from
Jul 5, 2019

Conversation

natcl
Copy link
Contributor

@natcl natcl commented Jul 4, 2019

  • Bugfix (non-breaking change which fixes an issue)
  • New feature (non-breaking change which adds functionality)

Proposed changes

Update JSONata to 1.6.5 to fix #2183

Checklist

  • I have read the contribution guidelines
  • For non-bugfix PRs, I have discussed this change on the mailing list/slack team.
  • I have run grunt to verify the unit tests pass
  • I have added suitable unit tests to cover the new/changed functionality

@knolleary
Copy link
Member

You'll need to update the individual package.json files as well.

Run node scripts/verify-package-dependencies.js to see which and rerun with --fix to update them and commit any changes

@natcl
Copy link
Contributor Author

natcl commented Jul 4, 2019

Thanks ! will do

@coveralls
Copy link

Coverage Status

Coverage increased (+0.04%) to 76.418% when pulling c2167a2 on natcl:patch-4 into f49d1ae on node-red:master.

@knolleary knolleary merged commit 083d6c5 into node-red:master Jul 5, 2019
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.

Change node: problem with JSONata and $lookup when used with a chain (~>) operator
3 participants