loopbackio / loopbackio/loopback-connector-mongodb
Getting warning options [writeConcern] is not supported
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 186
- Forks
- 238
- Avg merge
- 2h 49m
- Merged PRs (30d)
- 1
Description
## Steps to reproduce
I upgrade `loopback-connector-mongodb` version from `5.0.1` to `5.6.0`. It start showing error. I am loopback v3.
## Current Behavior
## Expected Behavior
## Link to reproduction sandbox
## Additional information
## Related Issues
_See [Reporting Issues](http://loopback.io/doc/en/contrib/Reporting-issues.html) for more tips on writing good issues_
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
The issue names no source file, test, or reproduction sandbox. Start by reproducing the upgrade from loopback-connector-mongodb 5.0.1 to 5.6.0 in a LoopBack 3 application and trace where the writeConcern warning appears. Done means the warning's cause and expected behavior are confirmed.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript, mongodb, nodejs
- Domain
- backend, databases
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100