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
In many places, I'm finding that retrieve_one will return None if the record_identifier is bad.
It would be more convenient for me if it would raise a RecordNotFoundError (which already exists), and I think is what this exception type was meant for. Then I can catch this and return a coherent message to the user. With just returning "none" silently, I'm having to build more error handling code.
I think there are several places that it just returns None -- maybe these should instead raise appropriate exceptions?
The text was updated successfully, but these errors were encountered:
In many places, I'm finding that
retrieve_one
will returnNone
if the record_identifier is bad.It would be more convenient for me if it would raise a
RecordNotFoundError
(which already exists), and I think is what this exception type was meant for. Then I can catch this and return a coherent message to the user. With just returning "none" silently, I'm having to build more error handling code.I think there are several places that it just returns
None
-- maybe these should instead raise appropriate exceptions?The text was updated successfully, but these errors were encountered: