[SERVER-53178] Mark legacy 'findandmodify' command name as unstable Created: 02/Dec/20 Updated: 29/Jan/21 Resolved: 29/Jan/21 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Task | Priority: | Major - P3 |
| Reporter: | Arun Banala | Assignee: | Joel Redman (Inactive) |
| Resolution: | Duplicate | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||
| Sprint: | Query 2021-01-11, Query 2021-01-25, Query 2021-02-08 | ||||||||
| Participants: | |||||||||
| Description |
|
The findAndModify command currently support two names. 'findAndModify' and 'findandmodify'. The legacy 'findandmodify' command name should not be allowed with apiStrict:true. |
| Comments |
| Comment by Arun Banala [ 29/Jan/21 ] |
|
|
| Comment by Joel Redman (Inactive) [ 29/Jan/21 ] |
|
Looks to be getting resolved as a side effect of |