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

Update required to LTL app due to Backend changes #49

Closed
HollyJoyPhillips opened this issue Jan 22, 2020 · 4 comments · Fixed by #216, #223 or #237
Closed

Update required to LTL app due to Backend changes #49

HollyJoyPhillips opened this issue Jan 22, 2020 · 4 comments · Fixed by #216, #223 or #237
Assignees
Labels
bug Something isn't working front-end Relates to front end issues lifetime-legal Relates to Lifetime Legal App

Comments

@HollyJoyPhillips
Copy link
Contributor

HollyJoyPhillips commented Jan 22, 2020

Location: https://dev.lifetime-legal-app.reapit.com/

Summary: The backend team have made changes to the /Contact endpoint which will require updates to the LTL App.

IMPORTANT See comment for details of code fixes

Contact Service

Communication

  • Previously the communication object contained ‘homephone’, ‘workphone’, ‘mobilephone’ and ‘email ‘
  • These are now separate fields so we will need to update the frontend to reflect this

Previous Setup:
image

New setup:
image

Addresses

  • Previously the Primary (0) and Secondary (1) addresses were contained within the object ‘addresses’. They are now separate fields ‘primaryAddress’ & ‘secondaryAddress’.
  • Primary and Secondary Addresses are used in the ‘Address History’ section on both AML and LTL.

Previous setup:
image

identityCheck service:

  • Previously the documents for the primary and secondary ID were contained in the object ‘documents’ and were listed as 0 and 1.
  • Following the changes, they are now separate fields ‘document1’ and ‘document2’. We will need to update ‘AML and LTL’ primary and secondary id sections to reflect this.

Previous:
image

New:
image

@HollyJoyPhillips HollyJoyPhillips added bug Something isn't working ltl labels Jan 22, 2020
duong-se pushed a commit that referenced this issue Jan 22, 2020
FIX loading on select identity component
willmcvay added a commit that referenced this issue Jan 24, 2020
@willmcvay
Copy link
Contributor

To make the build pass for mono-repo integration, have had to add ts-ignore to the breaking changes.
For the dev working on this, just grep // @ts-ignore #49 Breaking changes to API and you will see all the places the project is broken.

willmcvay added a commit that referenced this issue Jan 24, 2020
* [CLD-309] Upgrades elements to fix menu in mobile

* [CLD-309] Removes redundant code, fixes a test
willmcvay pushed a commit that referenced this issue Jan 24, 2020
@HollyJoyPhillips HollyJoyPhillips added lifetime-legal Relates to Lifetime Legal App and removed ltl labels Jan 28, 2020
@duong-se duong-se self-assigned this Jan 30, 2020
@duong-se
Copy link
Contributor

@HollyJoyPhillips I think it'll be effect AML checklist as well, so are there any ticket for AML checklist ?

@HollyJoyPhillips
Copy link
Contributor Author

@tanphamhaiduong Cuong already completed the changes required for AML in the last sprint

@duong-se
Copy link
Contributor

Moving back to TODO because blocked by permission of the app to access contact services

willmcvay added a commit that referenced this issue Feb 10, 2020
* fix: #49 update backend change for lifetime legal app

* fix: merged together AML & LTL fixes

Co-authored-by: Will McVay <[email protected]>
willmcvay pushed a commit that referenced this issue Feb 11, 2020
* fix: #49 break change on aml checklist and lifetime legal

* fix: pipeline error on demo site
nphivu414 pushed a commit that referenced this issue Apr 29, 2020
* fix: #49 update backend change for lifetime legal app

* fix: merged together AML & LTL fixes

Co-authored-by: Will McVay <[email protected]>
nphivu414 pushed a commit that referenced this issue Apr 29, 2020
* fix: #49 break change on aml checklist and lifetime legal

* fix: pipeline error on demo site
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment