fixes import on a typical schema-org.json #265
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
pvgenuchten
force-pushed
the
improve-schema-org
branch
from
5132291 to
b6ab6a0
Compare
pvgenuchten
force-pushed
the
improve-schema-org
branch
from
b6ab6a0 to
4e02046
Compare
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.
this adds methods get_first and get_all to get elm or get list
and fixes some parse errors
schema.org has a 0-N cardinality for most of its properties, if the value is single, the actual value is returned, if it is multiple a list of elements is returned
These utility functions provide option to grab the first or all elements, while checking their type to be literal or list, get-all returns list, get-first returns literal
some samples:
either fetch the json-ld from the html or open it in https://validator.schema.org/