Repository navigation
Gdgt 2618 add custom viz to the representation format schema - #35
Open
chodorowicz wants to merge 16 commits into
Open
chodorowicz wants to merge 16 commits into
chodorowicz wants to merge 16 commits into
Conversation
chodorowicz
marked this pull request as draft
October 15, 2026 14:21
chodorowicz
marked this pull request as ready for review
October 18, 2026 11:23
ranquild
approved these changes
Oct 21, 2026
chodorowicz
force-pushed
the
gdgt-2618-add-custom-viz-to-the-representation-format-schema
branch
from
October 27, 2026 14:17
8ed169c to
d3d9611
Compare
2 tasks done
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
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.
Description
Add custom vizualation's schema.
Depends on Gdgt 2618 add custom viz to the representation format schema by chodorowicz · Pull Request #84530 · metabase/metabase which needs to be merged first.
Chosen option:
Unpacked archive (unpack on export, pack on import)
name, version ranges and icon are visiblewithout extracting anything
byte-for-byte from the upload, so the stored bundle hash doesn't round-trip
Other options considered
tar stored inline
Bundle as a separate
bundle.tgznext to the YAMLwriter all assume text), so this needs new plumbing in the serialization layer