node-red / node-red/node-red-nodes
mongodb msg.collection does not return the correct value
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 1.1k
- Forks
- 612
- Avg merge
- 13h 57m
- Merged PRs (30d)
- 3
Description
When using node-red-mongodb, with a collection parsed via msg.collection property, and doing a find, the resulting msg.collection is not equal to the one I passed in. It seems to be equal to the last collection I queried using Robomongo (but haven't 100% validated this).
I patched it by setting the collection explicitly back to the original value. I would consider this a bug, or is this as designed?
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reproducing the issue in node-red-mongodb with a collection supplied through msg.collection and a find operation; compare the resulting value with the input and check whether the Robomongo observation is reproducible. Done means establishing the expected behavior and confirming that msg.collection is preserved or documenting why it is not.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript, mongodb
- Domain
- databases
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100