I am noticing some strange (broken) behavior with lists that are required in the [Foo!]! format. It's so easy to reproduce that others must have come across this but my searches are turning up nothing.
For example, if I deploy a new service with a field of notes: [String!]! it will deploy normally, but if I do another deploy straight afterwards it will say field 'notes' has been updated and the schema will show the type as [String!] even though types.graphql has not changed.
Reproduction
graphcool init foo
cd foo
Add a notes: [String!]! field to a type in types.graphql
Copying from here.
Current behavior
I am noticing some strange (broken) behavior with lists that are required in the
[Foo!]!
format. It's so easy to reproduce that others must have come across this but my searches are turning up nothing.For example, if I deploy a new service with a field of
notes: [String!]!
it will deploy normally, but if I do another deploy straight afterwards it will sayfield 'notes' has been updated
and the schema will show the type as[String!]
even thoughtypes.graphql
has not changed.Reproduction
graphcool init foo
cd foo
notes: [String!]!
field to a type intypes.graphql
graphcool deploy
graphcool deploy