kz930 opened a new pull request, #8344: URL: https://github.com/apache/texera/pull/8344
### What changes were proposed in this PR? Thirty visualizations implement `StandaloneCodeGenerator`, so a workflow that ends in a chart exports as a script that draws the same chart: the ones that read a table's columns — bar, line, pie, scatter, histogram, box and violin, funnel, strip, dot, waterfall, candlestick, heat map, ECDF, range slider, and the rest — the four that render a table or an image rather than a plot, and the six that draw a structure rather than a coordinate system: tree, network graph, sankey, hierarchy, icicle, dendrogram. A visualization emits a figure rather than a frame, so it is compared as one. The Plotly ones are compared number by number after both paths have drawn, which catches a difference in the data behind the picture without failing over a layout detail that carries no meaning. The two that emit an image or a rendered table are compared as the HTML that carries them. Network Graph is verified here rather than withheld. It had been flagged for placing its nodes differently on every run, which stopped being true when #7533 seeded the layout. Lifting that row showed something the reason had been hiding: the operator never called `manipulateTable`, the method it already had for dropping the rows that name no edge, so a null reached `add_node`, which refuses one outright. It is called now rather than reimplemented, since the code was already right. ### Any related issues, documentation, discussions? Part of #8325. Builds on #8327, which adds the trait and the verification. ### How was this PR tested? `OperatorBehaviorSpec` verifies all thirty against the operator they came from, drawing each twice and comparing the figures, across the configurations each one's schema offers — 42 runs, none withheld. `WorkflowOperator` passes in full at 2543 tests. ### Was this PR authored or co-authored using generative AI tooling? Generated-by: Claude Code (Opus 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]
