5 Replies
🤔 did this happen after an
ash_graphql
upgrade?Was on a very recent Git, pulled to check, then rolled back to the latest releases. All of this for
ash*
. All the same. Happy to try some older versions if you think there might be something there.that seems like a difficult error to hunt down really. The most useful thing to me would be to know which specific version the issue shows up in for the first time.
I ended up disabling the Absinthe schema and there were two errors that had been introduced: an incorrect module used for an attribute type and a relationship missing an
api
declaration.oh interesting
So it was not actually an error in the graphql layer
thats...frustrating