This behavior is inconsistent and forces me to handle a null participants entry in any FQL function that needs to work with the array, where I prefer to initialize with an empty array.
No updates yet if I’m not mistaking but I’ve been away on vacation, so I might be wrong. Ticket number is: PROD-807. This is only useful to communicate to other fauns about the problem. We don’t have public access to internal tickets atm.
Hi! Has this been solved?
I am experiencing a similar issue when trying to assign null to a field of [String!] type in hope of removing it. When I am inspecting the document in the “Collections” pane, it looks like I am getting what I want. Still, graphql returns an empty array instead when queried.
It seems like a very inconsistent behavior.