Hi - sorry I might be late to the party and I have...
# prisma-whats-new
s
Hi - sorry I might be late to the party and I haven’t looked at my Graphcool project for about a week, but now it looks like every 1:N or M:N Relationship now has to be declared like this:
tweets: [Tweet!]!
? Before,
tweets: [Tweet]
was viable
n
hey, that's correct. it should be noted that we read the latter as the former already, so it's no real change
s
hmm I get this error message which seems to be related to this -
"The schema is invalid: Invalid field type definition detected. Valid field type formats: Int, Int!, [Int!], [Int!]! for example.",
n
Yes, you need to change it to the former version now
s
ok thanks
n
but again, that's not a functional change in your case
s
however I read it that it’s a mandatory field because of the
!
, so I assume it has a different meaning in this context?
j
s
sorry I am not 100% up to speed on the GraphQL SDL - apologies if this is just how things are done in GraphQL 🙂
j
The change was made after I suggested it should be non-null, because it does not make sense that the list is null or there are null elements in the list. The list can still be empty though, so it's not a real restriction. nilan correct me if that's not the intention
👍 2
n
We always handled to many relation fields as @jan just mentioned
s
👍 thanks