-
Notifications
You must be signed in to change notification settings - Fork 22
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Syntax error indicator #62
Comments
On Tue, 23 May 2023 at 05:56, Jarno van Driel ***@***.***> wrote:
When I was playing around with with the demo I noticed it didn't seem to
report syntax errors but instead indicated: *"The input doesn't contain
structured data"*.
Is there any chance a future update will include syntax error reporting
(similar to that of Google's Rich Result Test or schema.org's validator)?
Nobody is currently working on that, but feel free
… —
Reply to this email directly, view it on GitHub
<#62>, or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AABJSGML4LNC67HBTIQEYM3XHSCTBANCNFSM6AAAAAAYLUHUUY>
.
You are receiving this because you are subscribed to this thread.Message
ID: ***@***.***>
|
I'm puzzled by the error report. Can you help me reproduce it? |
The initial comment was about validator,schema.org (closed source) and
enquires whether we might do syntax validation here someday
I think biggest issue is detailed error reporting?
…On Mon, 29 May 2023 at 09:00, ericprud ***@***.***> wrote:
I'm puzzled by the error report. Can you help me reproduce it?
—
Reply to this email directly, view it on GitHub
<#62 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AABJSGLWEKBS4473FOCLDNDXIRJQNANCNFSM6AAAAAAYLUHUUY>
.
You are receiving this because you commented.Message ID:
***@***.***>
|
My comment wasn't about validator.schema.org but about Schemarama. I was playing around with it to try to find out what it does or doesn't do. When I modified the default example and removed a comma at the end of the second line. That's when I got the feedback: "The input doesn't contain structured data". Code used:
|
My bad!
…On Mon, 29 May 2023 at 11:21, Jarno van Driel ***@***.***> wrote:
My comment wasn't about validator.schema.org but about Schemarama.
I was playing around with it to try to find out what it does or doesn't
do. When I modified the default example and removed a comma at the end of
the second line. That's when I got the feedback: *"The input doesn't
contain structured data"*.
Code used:
{
***@***.***": "https://schema.org/",
***@***.***": "http://example.org/recipe"
***@***.***": "Recipe",
"name": "Mom's World Famous Banana Bread",
"cookTime": "wwwwwwPT1H"
}
—
Reply to this email directly, view it on GitHub
<#62 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AABJSGJCLYSZAWXLXWBUHFLXIR2BBANCNFSM6AAAAAAYLUHUUY>
.
You are receiving this because you commented.Message ID:
***@***.***>
|
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
When I was playing around with with the demo I noticed it didn't seem to report syntax errors but instead indicated: "The input doesn't contain structured data".
Is there any chance a future update will include syntax error reporting (similar to that of Google's Rich Result Test or schema.org's validator)?
The text was updated successfully, but these errors were encountered: