The GitHub Actions job "Lint PR" on texera.git/fix/viz-attributetyperules-6795 has succeeded. Run started by GitHub user kz930 (triggered by kz930).
Head commit for run: a1e2979bcd744e105d6e07c14a48f0f46c120f8e / kary zheng <[email protected]> fix(QuiverPlot,RangeSlider): retarget numeric attributeTypeRules to real fields Both operators carried a class-level @JsonSchemaInject attributeTypeRules block constraining a field named "value" to numeric types, but neither declares a "value" field, so the rule matched nothing and no type constraint reached the frontend column pickers. Users could pick string columns for fields the operator only handles as numeric, failing at chart time instead of being prevented up front. Retarget each rule to the real @JsonProperty names: - QuiverPlot: x, y, u, v (all used as numeric vectors in ff.create_quiver and runtime-checked with isinstance(int, float)). - RangeSlider: Y-axis only (aggregated via groupby(X-axis)[Y-axis].mean()/.sum()); X-axis is only a grouping key and may be any type. Added regression tests reading the @JsonSchemaInject json() and asserting the attributeTypeRules keys are the real fields, not "value". Closes #6795 Co-Authored-By: Claude Opus 4.8 (1M context) <[email protected]> Report URL: https://github.com/apache/texera/actions/runs/29965587689 With regards, GitHub Actions via GitBox
