Repository navigation
The data app manifest is the app's serialized entity - #28
Merged
Merged
Conversation
Metabase now loads `data_app.yaml` as a `DataApp` entity: it carries `serdes/meta`, an `entity_id`, and its `slug`, and the validator checks it like every other entity file. The resources are loaded as the ordinary entity files they are: cards and actions name their creator, an action sits in the app's collection and may have no model, and a file that breaks the rules fails the pull, naming the file. HTTP actions are gone. Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
ranquild
approved these changes
Oct 2, 2026
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.
Metabase now loads
data_app.yamlas aDataAppentity: it carriesserdes/meta, anentity_id, and itsslug, and the validator checks it like every other entity file. The resources are loaded as the ordinary entity files they are: cards and actions name their creator, an action sits in the app's collection and may have no model, and a file that breaks the rules fails the pull, naming the file. HTTP actions are gone.