Skip to content

Fix undefined method transaction_id when LexisNexis PhoneFinder raises an exception#7074

Merged
mitchellhenke merged 1 commit intomainfrom
mitchellhenke/address-proofing-error
Oct 4, 2022
Merged

Fix undefined method transaction_id when LexisNexis PhoneFinder raises an exception#7074
mitchellhenke merged 1 commit intomainfrom
mitchellhenke/address-proofing-error

Conversation

@mitchellhenke
Copy link
Contributor

🛠 Summary of changes

Based on a failed job from New Relic, it appears to be an unintentional breakage from #6920, which introduced a new shape for proofing results.

undefined method `transaction_id' for #<Proofing::LexisNexis::ResultWithException

This PR adds a nil transaction_id to ResultWithException so the results have closer behavior. The AddressMockClient doesn't use ResultWithException so it's not straightforward to test.

…s an exception

changelog: Bug Fixes, Identity Verification, Fix undefined method transaction_id when LexisNexis PhoneFinder raises an exception
Copy link
Contributor

@aduth aduth left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

👍

Seems like something a base class would be well-suited to prevent against. It's difficult to tell what other classes might similarly be affected by this.

@mitchellhenke mitchellhenke merged commit d684ce5 into main Oct 4, 2022
@mitchellhenke mitchellhenke deleted the mitchellhenke/address-proofing-error branch October 4, 2022 14:18
jskinne3 pushed a commit that referenced this pull request Oct 12, 2022
…s an exception (#7074)

changelog: Bug Fixes, Identity Verification, Fix undefined method transaction_id when LexisNexis PhoneFinder raises an exception
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

Successfully merging this pull request may close these issues.

3 participants