Repository navigation
Chore/update vocabularies - #6
Merged
Merged
Conversation
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.
What does this PR do?
Upgrade the schema.org vocabulary to 30.1 and align the Google validator with the current Google structured data documentation. Every Google type now reports the properties Google recommends, except those Google makes conditional ("if applicable"), which are still checked when present and enforced by special rules when the document tells whether they apply.
The static schema.org context is now generated from the context schema.org publishes, so documents expand exactly as with
"@context": "https://schema.org", which fixes the "schema:" prefix and the "geo" term.Checklist
castor qa:phpunit:run)castor qa:cs)castor qa:phpstan)