RFC: Modularization (last mile)

[akphi]

Legend Studio core can still be broken down further; right now it still contains DSL-specifics and has the graph models, engine, and components all packed together. Following is a list of todos:

• Remove or move-out everything in legend-studio/src/utils (Refactor #410)
  • Move Logger to shared, keep CORE_LOG_EVENT in core
  • Eliminate usage of SourceInformation in TextEditorUtil
  • Move TextEditorUtil to legend-studio-components
  • Move logic inside of MappingResolutionUtil to stores or metamodels accordingly
• After elimitating legend-studio/src/utils/, break down legend-studio/src/models` into: (re-organization #422)
  • legend-server-sdlc
  • legend-server-depot
  • legend-graph
• Modularize legend-extension-dsl-diagram: this is currently complicated by the fact that we're using DiagramRenderer (which consumes Diagram) in ClassEditor (Upgrade to Typescript 4.4 #439)
• Feature request: Introduce extension mechanism consistently and exhaustively for class mapping #687
• Modularize PlanViewer - Feature request: Modularize plan viewer #717
• IMP Modularize AbstractPureGraphManager - publish doc website and improve Legend Studio analytics reporting #1266
• Modularize flat-data: legend-extension-store-flat-data - flat-data might get removed in the near future - if we finish RFC: Support for the unsupported #315 - maybe we could just remove all flat-data logic
• Modularize relational: legend-extension-store-relational
• After relational, move external format out of core potentially?
• Modularize service: legend-extension-dsl-service: We need to modularize how we start Legend Query
• Modularize generation: legend-extension-dsl-generation - This is considered part of core so we will likely not need to modularize it until much needed
• Modularize external-format: legend-extension-external-format (SchemaSet, Binding, etc.) - This will be motted as we really consider external format logic to be part of core, this will be consistent with engine
• Modularize mapping: legend-extension-dsl-mapping - be careful and really consider if we need to do this. This will break Studio down to a really really simple core though, which is a plus - This will be omitted as it's not really necessary and could cost us a lot to do, even https://github.com/finos/legend-engine is not doing this.

... and the last mile is often never easy to cross, but at least one does have it in their sight.