Remove problematic fields
n-wach opened this issue · 1 comments
n-wach commented
We don't request all fields anymore, and the errors we're currently handling shouldn't appear in normal use.
The handling complicates a lot of the request logic, and could potentially have very unexpected side effects (calling mutations multiple times, etc.). I think it's best if we remove all of this logic. If someone encounters a field that causes an error, it should really be reported and fixed in Conservator backend--not ignored