Skip to content

HDPI-3769 Regular expenses#1019

Open
libanAbdirahman1 wants to merge 7 commits intoHDPI-3764-income-expenditure-frontendfrom
HDPI-3769-Regular-expenses
Open

HDPI-3769 Regular expenses#1019
libanAbdirahman1 wants to merge 7 commits intoHDPI-3764-income-expenditure-frontendfrom
HDPI-3769-Regular-expenses

Conversation

@libanAbdirahman1
Copy link
Copy Markdown
Contributor

@libanAbdirahman1 libanAbdirahman1 commented Apr 1, 2026

Jira link

HDPI-3769

Change description

  • Introducing Regular expenses page to capture regular expenses type, amount & frequency.

Testing done

image

Security Vulnerability Assessment

CVE Suppression: Are there any CVEs present in the codebase (either newly introduced or pre-existing) that are being intentionally suppressed or ignored by this commit?

  • Yes
  • No

Checklist

  • commit messages are meaningful and follow good commit message guidelines
  • README and other documentation has been updated / added (if needed)
  • tests have been updated / new tests has been added (if needed)
  • Does this PR introduce a breaking change

arun-hmcts and others added 4 commits March 30, 2026 14:49
Co-authored-by: PadmaDeenadayalan <Padma.Deenadayalan@hmcts.net>
Co-authored-by: jessieharrigan <144362161+jessieharrigan@users.noreply.github.com>
Co-authored-by: padmakumari <padma.kumari@hmcts.net>
Co-authored-by: Gautham059 <gautham.bhikkumalla@hmcts.net>
@libanAbdirahman1 libanAbdirahman1 changed the title Hdpi 3769 regular expenses HDPI-3769 regular expenses Apr 1, 2026
@libanAbdirahman1 libanAbdirahman1 changed the title HDPI-3769 regular expenses HDPI-3769 Regular expenses Apr 1, 2026
@libanAbdirahman1 libanAbdirahman1 marked this pull request as ready for review April 1, 2026 14:10
@libanAbdirahman1 libanAbdirahman1 requested a review from a team as a code owner April 1, 2026 14:10
@libanAbdirahman1 libanAbdirahman1 requested review from linusnorton and saurabhvalsangkar-hmcts and removed request for a team April 1, 2026 14:10
moneyFromElsewhereDetails?: string;
householdBills?: YesNoValue;
householdBillsAmount?: PenceAmount;
householdBillsFrequency?: FrequencyValue;
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

Just for discussion - what do you think about creating a new type here, (and in the backend), which represents these three types that are repeated here? (i.e. does it apply / amount / frequency)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants