kz930 opened a new issue, #7395: URL: https://github.com/apache/texera/issues/7395
### What happened? Bubble Chart declares Color-Column with `required = true` and `@NotNull`, but the generated Python reads it only inside the Enable Color branch. So a freshly dropped Bubble Chart stays marked invalid until the user picks a color column, even when they want plain bubbles — and the column they pick is then never used. The property's own description already says it applies "if color is enabled". The sibling Ternary Plot has the same toggle-plus-column pair and gets it right: its color field is optional and the generated code guards on the column being non-empty. There is a second half. Even with Enable Color on, leaving the column blank is a reasonable thing to want. That path is unreachable today because of the required flag, but simply dropping the flag would hand `px.scatter` an empty string, which plotly rejects — the same failure #6792 fixed for Bar Chart. So the fix needs both: make the field optional, and treat an unset column as "no color" rather than passing it through. ### How to reproduce? 1. Drop a Bubble Chart, connect any source. 2. Fill X-Column, Y-Column, Z-Column. Leave Enable Color off. 3. The operator stays invalid and the workflow cannot run until a Color-Column is also chosen: <img width="1237" height="775" alt="Bubble Chart marked invalid with no Color-Column chosen" src="https://github.com/user-attachments/assets/a70db492-07e0-4bb5-b51f-312fb1fecdd3"; /> 4. Pick any column — the chart renders with no coloring; that column has no effect. ### Version/Branch 1.3.0-incubating-SNAPSHOT (main) ### Commit Hash (Optional) e7cd5b1ee030908455b65c79defc9c98e60a9372 -- 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]
