mirror of
https://github.com/apache/superset.git
synced 2026-09-05 06:51:48 +00:00
Verified that Pydantic always places inherited fields ahead of a subclass's own fields in model_fields, regardless of redeclaration position -- the mixin refactor as originally specced would have silently reordered DataBinding's rendered form (metrics before dataset picker). Add an explicit, opt-in field_order override to build_configuration_schema (ClassVar on the model, validated as an exact permutation of the schema's properties, ValueError on mismatch) so DataBinding can pin its field order back to today's exact sequence. Confirmed build_configuration_schema has no other call site today, so this is additive with no blast radius. Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>