GitHub user CaroFernando added a comment to the discussion: Proposal: Ditch Angular and Switch to a new frontend framework
Thanks @Yicong-Huang, agreed, and that’s what the data supports too: JointJS is framework-agnostic, so it can stay through the migration and the canvas can be its own decision later. You’re also right about the coupling: on current main, SharedModel and WorkflowGraph are canvas-neutral, but the Yjs↔canvas sync (SharedModelChangeHandler, SyncTexeraModel) and co-editor presence are written against JointJS. My “framework-neutral” meant Angular, not the canvas. Formly is the one piece I don’t think we can leave for later. @ngx-formly is Angular-only, so unlike JointJS the property panel (including the Yjs/Quill collab wrapper) has to be rebuilt in React eventually. It can stay in Angular until late in the migration, but it’s part of the cost of the framework decision. So I’d suggest: vote on the framework, keep JointJS, and list the property panel explicitly in the migration plan. GitHub link: https://github.com/apache/texera/discussions/9387#discussioncomment-19783589 ---- This is an automatically sent email for [email protected]. To unsubscribe, please send an email to: [email protected]
