You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
If the @id of a schema and the value of another field (say, url) are identical, parsing the document will result in a stack overflow.
It looks like this is caused by Nodes being keyed by the value of the node, but I'm enough of a layman to be unsure as to:
a. whether there was a good reason to do it in the first place
b. if there is a good way to fix and
c. if it's even allowable by the JSON-LD spec (I would assume it is, but again, I'm not intricately familiar with it)
I'm willing to put in the effort to try and get this fixed, but I'd need some guidance about what should be done to do so.
If the @id of a schema and the value of another field (say, url) are identical, parsing the document will result in a stack overflow.
It looks like this is caused by Nodes being keyed by the value of the node, but I'm enough of a layman to be unsure as to:
a. whether there was a good reason to do it in the first place
b. if there is a good way to fix and
c. if it's even allowable by the JSON-LD spec (I would assume it is, but again, I'm not intricately familiar with it)
I'm willing to put in the effort to try and get this fixed, but I'd need some guidance about what should be done to do so.
Example JSON-LD:
Example test script:
Expected output:
Actual output:
The text was updated successfully, but these errors were encountered: