You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
There are multiple points in the aserializer.fields.base where is an expect all.
This is vary frustrating because it caches every error and tells you that it is a SerializerFieldValueError.
This has cost us 5h of debugging to find our programming error !!!
is it required to catch all??
except:
raise SerializerFieldValueError(self._error_messages['invalid'], field_names=self.names)
The text was updated successfully, but these errors were encountered:
On Thu, Dec 04, 2014 at 08:13:42AM -0800, alex wrote:
There are multiple points in the aserializer.fields.base where is an expect
all.
This is vary frustrating because it caches every error and tells you that it is
a SerializerFieldValueError.
This has cost us 5h of debugging to find our programming error !!!
is it required to catch all??
except:
raise SerializerFieldValueError(self._error_messages['invalid'], field_names=
self.names)
—
Reply to this email directly or view it on GitHub.*
There are multiple points in the aserializer.fields.base where is an expect all.
This is vary frustrating because it caches every error and tells you that it is a SerializerFieldValueError.
This has cost us 5h of debugging to find our programming error !!!
is it required to catch all??
except:
raise SerializerFieldValueError(self._error_messages['invalid'], field_names=self.names)
The text was updated successfully, but these errors were encountered: