feat: Add support for extended JSON in mongo node #12574
+13
−3
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Summary
This PR enhances the MongoDB node by adding support for Extended JSON (EJSON). With this update, users can now leverage EJSON features, such as converting values to specific types like
"$date"
, making it easier to handle complex MongoDB operations directly within the node.How to test:
{ "createdAt": { "$date": "2025-01-01T00:00:00Z" } }
.Note:
EJSON.parse
will handle both normal JSON and Extended JSON gracefully.Related Linear tickets, GitHub issues, and Community forum posts
https://community.n8n.io/t/mongodb-date-objects-in-queries/40935/6
https://community.n8n.io/t/mongo-node-prefiltering-by-dates/4124
Review / Merge checklist