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

EPP-163, 164 Under 18 Redirection - Edit Journey #77

Open
wants to merge 9 commits into
base: master
Choose a base branch
from

Conversation

vivekkumar-ho
Copy link
Contributor

@vivekkumar-ho vivekkumar-ho commented Feb 17, 2025

What?

https://collaboration.homeoffice.gov.uk/jira/browse/EPP-163 - Amend - Edit Journey for DOB page
https://collaboration.homeoffice.gov.uk/jira/browse/EPP-164 - New & Renew - Edit Journey for DOB page

Why?

EPP-163 & EPP-164 are combined into a single PR because they are using the same behaviour and have same implementation logic. Grouping them together minimise redundant reviews, and duplicate code effort.

How?

New behaviour has been added to validate the date and redirect if required
Helper is created to verify the edit journey

Testing?

Local and branch testing

Screenshots (optional)

Anything Else? (optional)

Check list

  • I have reviewed my own pull request for linting issues (e.g. adding new lines)
  • I have written tests (if relevant)
  • I have created a JIRA number for my branch
  • I have created a JIRA number for my commit
  • I have followed the chris beams method for my commit https://cbea.ms/git-commit/
    here is an example commit
  • Ensure drone builds are green especially tests
  • I will squash the commits before merging

@vivekkumar-ho vivekkumar-ho changed the title WIP: EPP-163 edit dob redirection WIP: EPP-163, 164 Under 18 Redirection - Edit Journey Feb 18, 2025
@vivekkumar-ho vivekkumar-ho changed the title WIP: EPP-163, 164 Under 18 Redirection - Edit Journey EPP-163, 164 Under 18 Redirection - Edit Journey Feb 18, 2025
@vivekkumar-ho vivekkumar-ho self-assigned this Feb 18, 2025
Copy link

@william-gu-hof william-gu-hof left a comment

Choose a reason for hiding this comment

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

Logic looks good, just a question about a step on the amend journey, not sure what it is for. I've not gone through the tests in details

@@ -207,6 +212,10 @@ module.exports = {
fields: ['amend-countersignatory-document-type'],
next: '/confirm'
},
'/birth-certificate': {
fields: [],

Choose a reason for hiding this comment

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

no fields on this step? Is this step used for these 2 tickets?

Copy link
Contributor Author

@vivekkumar-ho vivekkumar-ho Feb 18, 2025

Choose a reason for hiding this comment

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

@william-gu-hof This is just a placeholder route to validate the navigation. The page is not built yet.

No, this is only used in amend. new-renew /birth-certificate route already exists so I didn't add that.

@@ -5,6 +5,9 @@
"name-on-licence": {
"header": "What is your name on the licence?"
},
"date-of-birth": {
"header": "What is your date of birth?"
},
Copy link
Contributor

Choose a reason for hiding this comment

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

I noticed that there was a bug with the page header and now I realise why since the path name changed from amend-date-of-birth to date-of-birth can you remove the unused code please from line 17th?

image

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