-
Notifications
You must be signed in to change notification settings - Fork 7
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
DFPL-2326 c110a Design Changes to Applicant's details (LA) #5812
base: master
Are you sure you want to change the base?
Conversation
"ID": "EnterApplicantLa", | ||
"CaseEventID": "enterApplicantDetailsLA", | ||
"CaseFieldID": "applicantContact", | ||
"ListElementCode": "fullName", |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Wonder if we could split this out into first name/last name? Asked service for the applicant is respondent flow and they said it was fine (think Alistair's doing it this way now on his PR).
"ID": "EnterApplicantLa", | ||
"CaseEventID": "enterApplicantDetailsLA", | ||
"CaseFieldID": "applicantContactOthers", | ||
"ListElementCode": "fullName", |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Guess similar comment here - might be good to be consistent.
JIRA link (if applicable)
https://tools.hmcts.net/jira/browse/DFPL-2326
Change description
DFPL-2326 c110a Design Changes to Applicant's details (LA)
Does this PR introduce a breaking change? (check one with "x")