[DOCS-11823] $geoNear field options should be in order Created: 20/Jun/18 Updated: 30/Oct/23 |
|
| Status: | Closed |
| Project: | Documentation |
| Component/s: | manual, Server |
| Affects Version/s: | None |
| Fix Version/s: | Server_Docs_20231030 |
| Type: | Improvement | Priority: | Trivial - P5 |
| Reporter: | Nic Cottrell | Assignee: | Andrew Aldridge |
| Resolution: | Won't Do | Votes: | 0 |
| Labels: | triage | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Participants: | |
| Days since reply: | 1 year, 14 weeks, 2 days ago |
| Epic Link: | DOCSP-1769 |
| Story Points: | 0.1 |
| Description |
|
---------------------------- Original DescriptionI'm looking at https://docs.mongodb.com/manual/reference/operator/aggregation/geoNear/ The table of fields is in a weird order - it's not alphabetical or by importance. Shouldn't required fields near and distanceField be first, then optional fields in alphabetical ? DescriptionScope of changes (files that need work and how much)Impact to other docs outside of this productMVP (work and date?)Resources (e.g. Scope Docs, Invision) |
| Comments |
| Comment by Education Bot [ 31/Oct/22 ] |
|
Hello! This ticket has been closed due to inactivity. If you believe this ticket is still important, please reopen it and leave a comment to explain why. Thank you! |