Repository navigation
feat: say "Convert to Vega-Lite" and create custom viz under viz/ - #10044
Merged
Merged
Conversation
User feedback on the custom components feature (#9850), applied before 0.91 ships either convention: - The component editor action and its tooltip, confirmation, progress and result notifications now say "Convert to Vega-Lite" instead of "Eject to Vega-Lite" (en + es). Message keys and code identifiers keep the internal "eject" name. - New custom viz files are created under `viz/` instead of `viz_library/`. The folder is only a convention for new files; the parser keys on `type: component`, so existing `viz_library/` projects keep working. - Docs and the AI developer instructions use the new term and folder.
AdityaHegde
approved these changes
Oct 21, 2026
8 tasks
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.
User feedback on custom components (#9850), applied before 0.91 ships either convention:
viz/instead ofviz_library/. The folder is only a convention for new files; the parser keys ontype: component, so existingviz_library/projects keep working.Intended for cherry-pick into
release-0.91.Checklist: