feat(extensions): expose Superset categorical color schemes to extensions#39226
Draft
feat(extensions): expose Superset categorical color schemes to extensions#39226
Conversation
…ions Add a `colors` module to superset-core that lets extensions read Superset's registered categorical color palettes without taking a direct dependency on @superset-ui/core. Pattern: ExtensionsStartup injects the live CategoricalSchemeRegistry singleton into superset-core at startup via `registerCategoricalSchemeRegistry()`. Extensions then call `colors.getCategoricalSchemeNames()` / `colors.getSchemeColors(name)` through the federated `@apache-superset/core` module — the same singleton, so palettes registered by the host are visible. Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
✅ Deploy Preview for superset-docs-preview ready!
To edit notification comments on pull requests, go to your Netlify project configuration. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
colorsmodule to@apache-superset/coreexposing the host app's registered categorical color palettes to extensionsExtensionsStartupinjects the liveCategoricalSchemeRegistrysingleton at startup viaregisterCategoricalSchemeRegistry()colors.getCategoricalSchemeNames()/colors.getSchemeColors(name)through the federated module — same singleton, so all palettes registered by the host (Superset defaults, custom themes) are visibleThis is a prerequisite for the Notebook extension's Mermaid palette selector, which lets users pick any Superset color scheme to drive Mermaid pie/diagram fills instead of a hardcoded fallback palette.
Note: This PR is intended to merge after #39171 (Tier 1+2 storage) lands, since both touch
ExtensionsStartup.tsxandsuperset-core/src/index.ts.Before/After
Before: Extensions had no way to access Superset's color palettes; the notebook extension used a hardcoded 8-color AntD palette for Mermaid diagrams.
After: Extensions can enumerate and read any registered Superset categorical color scheme. The Notebook extension shows a palette selector in the Mermaid cell header.
Test plan
superset-corebuilds cleanly (npm run buildinpackages/superset-core)colors.getCategoricalSchemeNames()returns an array of scheme names from within an extensioncolors.getSchemeColors('supersetColors')returns the expected hex array🤖 Generated with Claude Code