Suddenly nothing seems to work for me. Is it just...
# prisma-whats-new
p
Suddenly nothing seems to work for me. Is it just me? Getting this error: { "requestId": "cj1van6zbelr60123ftxbm101", "error": "Whoops. Looks like an internal server error. Please contact us in Slack (https://slack.graph.cool) and send us your Request ID: cj1van6zbelr60123ftxbm101" }
i
@patrickj happened to me because of the certain fields / model names ( like
viewer
or
node
or ending with
Id
)
👍 1
p
Ah! I added some fields ending with Id at about the time things stopped working. Thanks!
Yep. That was it. Thanks again.
i
no worries, @nilan better to put list of fields to avoid in bold red asap 😃
p
Is it odd that the import examples use "oldId" fields? Looks like sometimes it's okay and sometimes it isn't.
i
I think issues with
..Id
start when adding relations
s
Hi Ilia and Patrick. The issue arrises when two fields in a mutation has the same name. For example in a create mutation you are able to directly add the new node to a relation by setting the id of the related node. It’s this relation field that can conflict with a field you added that ends wit
id
.
p
Thanks @sorenbs, That aligns with what I'm seeing.