fix: commercial baseline — share export redaction, index parse, README - #692
Merged
Merged
Conversation
- Redact comments/example_value on public share SQL and index-design exports - Fix functional-index false positives in index redundancy detection - Align README with shipped auth/ERD/share/export capabilities
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.
Summary
Closes the remaining commercial-baseline gaps after the open-PR drain:
example_valuestripped). Tests assert secrets never appear.lower(email)are no longer mis-parsed as plain-column duplicates (re-land of fix(spec): stop mis-parsing functional indexes as a duplicate of a plain column #683 without lockfile churn).Test plan
PYTHONPATH=. pytest -q tests/test_api_share.py tests/test_index_redundancy.py(12 passed)