This repository was archived by the owner on Sep 1, 2026. It is now read-only.
Repository navigation
Conversation
This package's charter is 'GoodData metadata as SQLite, as easy as possible': the export engine plus schema-adjacent views that describe the exported tables 1:1. The reachability views encode an analytical METHOD (LDM-graph comparability) and evolve with the CI check that consumes them — a different change cadence and the most complex SQL here by far. They now live in the toolkit's own view layer, which its SQL-view overlay serves to every consumer identically. The category: validation grouping stays for future schema-adjacent checks.
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 subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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.
Follow-up to #45 after a placement review: this package should stay as easy as possible — export engine + schema-adjacent views. The reachability views encode an analytical method and evolve with the CI check that consumes them, so they move to the toolkit's own view layer (same visibility for every toolkit consumer via its SQL-view overlay). Tagged
v1.18.1.🤖 Generated with Claude Code