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
Is working fine on the first entrytype and section I used it on. When trying to use the exact same field (mndLinks) on a different section and type, I get the error:
Field \"save_thesection_thetype_Entry\" argument \"mndLinks\" requires type mndLinks_TableRowInput, found [{col1: \"test\", col2: \"uirl\"}].
Not sure why it expects a table to not be an array of mndLinks_TableRowInput in this case, but it is for the working entry type? Figured it might be a bug, but upgraded to the latest version and still the same thing.
But also, if I do change the data to not be an array, it throws an underlying error:
Which tells me that it is the graphQL schema that is wrong, but I have no idea on how to fix it...?
EDIT: I just noticed, that if I remove this field from the first EntryType, the schema becomes correct. As soon as I re-add it, the same error appears. Must surely be a bug.
Steps to reproduce
Create a table field, add it to one entry type.
Add the same field to a second entrytype (I have in in a different site and section as well), inspect the graphQL schema, it is not define as an array
Description
Given this mutation (which adds rows to a table)
Is working fine on the first entrytype and section I used it on. When trying to use the exact same field (mndLinks) on a different section and type, I get the error:
Field \"save_thesection_thetype_Entry\" argument \"mndLinks\" requires type mndLinks_TableRowInput, found [{col1: \"test\", col2: \"uirl\"}].
Not sure why it expects a table to not be an array of mndLinks_TableRowInput in this case, but it is for the working entry type? Figured it might be a bug, but upgraded to the latest version and still the same thing.
But also, if I do change the data to not be an array, it throws an underlying error:
Which tells me that it is the graphQL schema that is wrong, but I have no idea on how to fix it...?
EDIT: I just noticed, that if I remove this field from the first EntryType, the schema becomes correct. As soon as I re-add it, the same error appears. Must surely be a bug.
Steps to reproduce
Additional info
Amazon S3 1.3.0
PathTools 1.0.7
Redactor 2.8.8
Redirect Manager 1.1.1
Retcon 2.3.0
Super Table 2.6.8
Tags 1.0.9
Webhooks 2.3.3
The text was updated successfully, but these errors were encountered: