Repository navigation
docs: correct MIGRATION jsonSchema -> toCodecJson annotation name - #136
Open
detail-app[bot] wants to merge 1 commit into
Open
detail-app[bot] wants to merge 1 commit into
detail-app[bot] wants to merge 1 commit into
Conversation
|
This branch has not been deployed
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.
Section 9 of MIGRATION.md said sentinel and Firestore type schemas carry
jsonSchemaannotations, but the underlying implementation was replaced withrepresentation+toCodecJsonlinks. The termjsonSchemano longer matches any option name in the code, so the migration guide contradicted the updated AGENTS.md JSON Schema section and would mislead anyone upgrading from v0.x into using a non-existent annotation.Introduced by commit 2c6dc8a (@fwal, #134)
Doc Drift PRs can be configured here.