Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

record.errors is always non-empty because it contains a "null" error #590

Open
ericcj opened this issue Aug 18, 2023 · 1 comment
Open

Comments

@ericcj
Copy link
Contributor

ericcj commented Aug 18, 2023

at least after an upsert maybe after any request it looks like this "errors":[{"type":null,"code":null,"message":null}]

@gbs4ever
Copy link
Contributor

gbs4ever commented Mar 29, 2024

yes , i just had this last week this code used to work @transfer_order.errors.nil? || @transfer_order.errors.empty? vs what I had to change @transfer_order.errors.nil? || @transfer_order.errors.empty? ||@transfer_order.errors.all? { |error| error.message.nil? }

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants