xuang7 opened a new pull request, #7641: URL: https://github.com/apache/texera/pull/7641
### What changes were proposed in this PR? This PR adds the controller that puts an operator on the canvas, the step every demo builds around. Changes: - `OperatorControllerBuilder.insertViaDrag`: locates the operator in the left panel by its metadata group hierarchy (falling back to the search box), drags it onto the canvas, and wires it up. Wiring follows the operator's port topology: source operators connect nothing, single-input operators connect to the anchor, and two-input operators pull a second edge from a given upstream port into a given input port. - `OperatorGroups`: flattens the operator group tree into name -> path, shared metadata used to walk the nested group panels. - Adds the module's dependency on the operator-metadata modules, with the jackson overrides that keep Playwright's transitive jackson on the repo-wide version. - Extends `Utils` (canvas-geometry helpers and a shared name normalizer) and the timing constants the controller waits on. - Four `data-testid` hooks (left-panel Operators button, operator search input, per-operator list items `operator-item-<type>`, and the property-panel title the controller waits on after a drop), each covered by a guard test in the component's existing spec. ### Any related issues, documentation, discussions? Closes #7521 Depends on #7600. ### How was this PR tested? No behavior change to any existing module. `sbt DemoVideoGenerator/compile`, `scalafmtCheck`, and `scalafix --check` all pass; the three touched component specs (65 tests, including the new guard tests) pass. The drag-and-connect flow was exercised against a local deployment across all three port topologies (source, single-input, two-input join). ### Was this PR authored or co-authored using generative AI tooling? Generated-by: Claude Code (Claude Fable 5) -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
