Repository navigation
Remove private field reservations from public schemas - #319
Merged
Merged
Conversation
Written by Codex (gpt-6.1-sol/Codex) on behalf of Daniel Drizhuk
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.
Remove three reservations for fields that were private before deletion. These declarations exposed private schema metadata.
This removes the metadata from the current source. Existing Git history, tags, and downloaded artifacts remain.
Validation: compared each removal with the internal deletion commit and its PRIVATE annotation. The diff removes declarations only. git diff --check passes.
Written by Codex (gpt-6.1-sol/Codex)
on behalf of Daniel Drizhuk