Skip to content
This repository was archived by the owner on Apr 22, 2021. It is now read-only.

Add support for only checking year of birth in LexisNexis (LG-3706)#52

Merged
zachmargolis merged 3 commits intomainfrom
margolis-dob-year-only
Jan 27, 2021
Merged

Add support for only checking year of birth in LexisNexis (LG-3706)#52
zachmargolis merged 3 commits intomainfrom
margolis-dob-year-only

Conversation

@zachmargolis
Copy link
Contributor

@zachmargolis zachmargolis commented Jan 26, 2021

Builds on: 18F/identity-lexisnexis-api-client-gem#20

  • Adds a new dob_year_only top-level argument to the lambda payload body
  • When enabled and we're checking for an AAMVA state, this:
    1. flips the order of checking so that AAMVA is first
    2. passes dob_year_only into LN, so that LN only sends DOB

Next steps:

  1. Update the IDP to reference this and pass in the new param
  2. Test that new param in staging (w/o background processing) to make sure this all actually works

it 'only sends the birth year to LexisNexis (extra applicant attribute)' do
expect(aamva_proofer).to receive(:proof).and_return(Proofer::Result.new)
expect(lexisnexis_proofer).to receive(:proof).
with(hash_including(dob_year_only: true)).
Copy link
Contributor

Choose a reason for hiding this comment

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

dob_year_only: dob_year_only

Copy link
Contributor

@stevegsa stevegsa left a comment

Choose a reason for hiding this comment

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

LGTM

Copy link

@mitchellhenke mitchellhenke left a comment

Choose a reason for hiding this comment

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

👍🏼

I don't think the IDP would/should have any issues, but will be keeping an eye out for whether switching the order of LN -> AAMVA to AAMVA -> LN in some cases causes issues.

@zachmargolis
Copy link
Contributor Author

I don't think the IDP would/should have any issues, but will be keeping an eye out for whether switching the order of LN -> AAMVA to AAMVA -> LN in some cases causes issues.

I agree, the ordering switch is the riskiest part of this, but I didn't see another way to accomplish the goal of the ticket

@zachmargolis zachmargolis merged commit 696ca97 into main Jan 27, 2021
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants