chore: move introspection logic into pg_introspect#16
Merged
Conversation
Adds enum-mapping tests and a golden fixture catalog with a frozen content_hash to guard against silent drift in field ordering or upstream pg_introspect changes that would invalidate stored snapshots. Also runs cargo fmt across the workspace (server.rs). Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
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
1 participant
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.
Switched the snapshot logic to the external pg_introspect crate. This change does not break anything, snapshots are 100% byte identical. The motivation is downstream, future fixturize and dryrun will share data masking rules in later releases.
For #15