[COMPASS-3081] Support Extended JSON in the Query Bar Created: 23/Aug/18 Updated: 07/Apr/23 Resolved: 27/Mar/19 |
|
| Status: | Closed |
| Project: | Compass |
| Component/s: | Query Bar |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Task | Priority: | Minor - P4 |
| Reporter: | Durran Jordan | Assignee: | Unassigned |
| Resolution: | Won't Fix | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Sprint: | Iteration Bison |
| Description |
|
Compass dropped support for extended JSON syntax in the query bar and needs to support it again. This ticket is a placeholder for the following items to be expanded on:
1: Support for Extended JSON in the Query Bar. 2: Support for Extended JSON in the Agg Pipeline Builder. 3: Requiring users to select what their input type is in both areas, as a precursor to custom language modes. |
| Comments |
| Comment by Brian Blevins [ 20/May/20 ] |
|
If this feature is important for your workflow, please vote for the idea on MongoDB's feedback engine. |
| Comment by Frederick Zhang [ 30/Apr/19 ] |
|
As one who's new to MongoDB, this is causing a lot of troubles for me. An aggregation worked in mongo shell but failed in MongoDB Compass when I tried to showcase the intermediate results to others. Then I found It's surprising to me that this problem didn't draw much attention. I think even if there's no plan to support extended JSON for now, Compass should give users a more sensible error message rather than a generic syntax error. |
| Comment by Massimiliano Marcon [ 27/Mar/19 ] |
|
Not much activity on this ticket. Closing for now, we'll reconsider later. |
| Comment by Massimiliano Marcon [ 27/Mar/19 ] |
|
We are not going to work on this at this time. Please follow up if you still think it's important. |