mirror of
https://github.com/apache/superset.git
synced 2026-05-28 11:15:24 +00:00
1fffd9d832
Most touchups fit declarative YAML cleanly (typos, ISO codes, repositions, dissolves, composites). A few don't — e.g., the France-with-Overseas notebook drops a specific sub-polygon by index to avoid visual conflict with Corsica. Add a `procedural/` directory of small, named, single-purpose Python scripts as an escape hatch. Build orchestrator runs YAML transforms first, then iterates procedural/*.py in numeric order. Why this is much better than the notebook for the same content: - Each fix is a separate file → conflicts localize to one fix at a time, not "the whole notebook touched the same cell" - No kernel state, no output churn, pure functions on data - Naming forces documentation; reviewers see add/remove at a glance - Bounded growth: a 50-file procedural/ dir is annoying enough to signal "push back into YAML or upstream"; the notebook had no such signal and just bloated Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>