I am getting this response validation error when I use 8.x-2.0-rc1:
{
"property": "relationships.agency.data.type",
"pointer": "\/relationships\/agency\/data\/type",
"message": "Does not have a value in the enumeration [\"taxonomy_term--agency\"]",
"constraint": "enum",
"context": 1,
"enum": [
"taxonomy_term--agency"
]
},
It goes away if I manually unset the 'enum' from where it is, deep in the nested schema array. But I suspect that's not really fixing the problem. I'm happy to try some debugging if anyone has ideas.
If it helps, this site has a taxonomy vocabulary resource which is being overridden by this module from 'taxonomy_term--agency' to just 'agency'.
Comments
Comment #2
brockfanning commentedThis is not a neat fix, but the attached patch does prevent the reported validation errors for me. At the least maybe this helps illustrate the issue.
Also for reference, this offending 'enum' element is getting added in the Schemata module here.
Comment #3
brockfanning commentedRemoving irrelevant change.
Comment #4
logickal commentedWe also saw a lot of these messages with our custom entities, possibly also related to the Schemata validation issues reported in JSONAPI #2958370: Schemata + JSON API: "JSON API response failed validation" error message on node endpoints...
Comment #5
logickal commentedI'm fairly certain this has been resolved...
Comment #6
e0ipsoThanks for bubbling this up @logickal. I'm sorry this took so long @brockfanning :-(
I'm OK with the fix.