RFC: Rework editor modes #317
Labels
Application: Studio
Issues related to Legend Studio application
Studio Core Team
Opened by a member of the Studio core team
Type: Discussion
Type: Refactor
Milestone
💬 Request for Comments
Within Studio, we currently support 3 modes:
editor
,viewer
, andreview
, each is somewhat being treated differently: e.g.viewer
mode does not allow editing elements,review
mode does not allow viewing and working with the element, etc. Whenquery builder
becomes standalone, we might need to yet support another mode. What we realize is, these modes are not too far off from one another. In fact, we are trying to bring them closer in functionalities - see #297.In fact, we should consider all the flows and just make them different in a very small set of features. Instead of thinking that we should create a brand new mode without any functionality and then adding them one by one (like what we're trying to do in #297), we probably should start using
EditorStore
and having ways to disable certain features if that's cleaner. i.e. starts from the full one -editor mode
- and see what we can turn offImplementation Plan
EditorMode
- studio: rework handling of multiple SDLC instances #642EditorMode
for places we need to useisInViewerMode
etc. NOTE: we should also review the content of the old implementation plan.ViewerStore
as well as there are many ways to launchViewer
mode nowImplementation Plan (OLD - TO BE REVISED)
git checkout -b <branch_name>
behaviour)The current implementation is not bad, what we should do, however, is to add boolean flags when we configure
EditorStore
for the first time instead of relying on the flags likeisInViewerMode
, etc.The text was updated successfully, but these errors were encountered: