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
Is there any intent/interest in accepting atoms as error messages? For instance if the reason a mutation errors is its unauthenticated or the record it is attempting to change doesn't exist, :unauthorized or :not_found would be the expected error return, but if I want this library to parse that into the message I'd have to check to see if I'm returning an atom everywhere I might and stringify it.
Is adding a function head that converts atoms to binaries to convert_to_payload/1 a reasonable thing, or is the assumption that users of this library catch simple atom errors and format them into more verbose errors?
The text was updated successfully, but these errors were encountered:
Is there any intent/interest in accepting atoms as error messages? For instance if the reason a mutation errors is its unauthenticated or the record it is attempting to change doesn't exist,
:unauthorized
or:not_found
would be the expected error return, but if I want this library to parse that into the message I'd have to check to see if I'm returning an atom everywhere I might and stringify it.Is adding a function head that converts atoms to binaries to
convert_to_payload/1
a reasonable thing, or is the assumption that users of this library catch simple atom errors and format them into more verbose errors?The text was updated successfully, but these errors were encountered: