kz930 opened a new pull request, #7341: URL: https://github.com/apache/texera/pull/7341
### What changes were proposed in this PR? Wind Rose's radial value and Bubble Chart's z column are both consumed as magnitudes, and neither declared an `attributeTypeRules` entry, so the property form offered every column and accepted a string one. Each now declares `integer`, `long` or `double`, the way Range Slider's y-axis and Radar Chart's value columns already do. The other pickers are deliberately left alone: Wind Rose's angle is a direction label and Bubble Chart's x and y are positions, all of which take any type the way a scatter plot's axes do. ### Any related issues, documentation, discussions? Closes #7324. Same class of gap as #7250, which covered a different set of operators. ### How was this PR tested? `WindRoseChartOpDescSpec` and `BubbleChartOpDescSpec` pass. The behaviour each rule prevents was reproduced first: rendering the same three-row frame with a numeric column and with a string one, Wind Rose's `radialaxis.type` comes out `linear` with range 0 to 4.2 for the numeric column and `category` with range −0.11 to 2.11 for the string one — the wedges drawn at ordinal positions rather than lengths, with no error — and this holds even when every value is a number written as text. Bubble Chart raises `TypeError: unsupported operand type(s) for /: 'str' and 'int'` on either. Both rule keys were checked against the property they name, since a key matching no property is silently inert (#7210). ### Was this PR authored or co-authored using generative AI tooling? Generated-by: Claude Code (Claude 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]
