[COMPASS-5949] Make Editors accept both EJSON and Shell syntax Created: 12/Jul/22  Updated: 28/Sep/23

Status: Open
Project: Compass
Component/s: UI / UX
Affects Version/s: None
Fix Version/s: None

Type: Task Priority: Major - P3
Reporter: Anna Henningsen Assignee: Unassigned
Resolution: Unresolved Votes: 1
Labels: code-editors
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Duplicate
is duplicated by COMPASS-5898 Use JavaScript editor instead of JSON... Closed
Related
related to COMPASS-5853 Code formatting support for stage editor Closed
Story Points: 8
Sprint: Iteration Herring, Iteration Isopod, Iteration Jellyfish, Iteration Kraken, Iteration Lobster, Iteration Manatee, Iteration Narwhal

 Description   

Currently, some of our editors accept EJSON (Insert/Edit in CRUD), while some accept Shell syntax (e.g. Agg pipeline builder). We do not display information about which editor accepts which kind of input.

I think we can and should add a toggle to the Editor component that allows switching between the two modes while editing (in the UI, this could look similar to what we’re working out for code formatting in COMPASS-5853), so that the ambiguity is resolved without requiring users to update their workflows.



 Comments   
Comment by Githook User [ 25/Jul/22 ]

Author:

{'name': 'Anna Henningsen', 'email': 'anna@addaleax.net', 'username': 'addaleax'}

Message: chore: add BSON doc editor component, use for FLE2-related fields COMPASS-5949

This partially addresses COMPASS-5949 and might be useful as a starting
point for what approach we want to take here.

Currently, this creates a new `BSONDocumentEditor` component
specifically for editor instances that are targeting BSON documents
(which most of our editors do), adds an EJSON/Shell syntax switch
to it, and centralizes parsing/JS serialization in a single location.
Branch: 5949-dev
https://github.com/mongodb-js/compass/commit/1e92cd4f2fadb80eead39addaa1f058bbdba4cb0

Generated at Wed Feb 07 22:41:24 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.