Overhaul schema validation #121
Merged
Conversation
This file contains 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.
Overhauls schema validation to use custom-coded Schema.org types rather than https://github.com/blurry-dev/pydantic2-schemaorg/.
Performance of
pydantic2-schemaorgwas slow and the code was tricky to maintain. The approach of this PR is to focus on Schema.org types that Google uses for rich search results, which is the main benefit of this feature.Not all schema types and fields are finished, but this is a good start. See here for the Google docs on their supported schema types:
https://developers.google.com/search/docs/appearance/structured-data/search-gallery