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

144220 Income questions updates #991

Merged
merged 11 commits into from
Jan 10, 2024
Merged

144220 Income questions updates #991

merged 11 commits into from
Jan 10, 2024

Conversation

shawn320
Copy link
Contributor

@shawn320 shawn320 commented Dec 29, 2023

144220 - Income questions updates

Description

Added a new field for salary exemption under Income category.

Calculation updates:
To calculate income for GIS, ALW and ALWS, take the input from the first field and SUBTRACT these amounts from the second field:
the first $5,000
50% of next $10,000
The maximum subtraction possible is $10,000 if input is $15,000 or more.

To calculate income for partner GIS, ALW and ALWS, apply the same calculation to the inputs.

To compare against recovery threshold for OAS pension, use income from first field only (no subtractions).

Updated error handling: Second income field cannot be greater than net income, also apply to partner income.

Updated income question: The income question, hint expand text, and error message should change dynamically based on user's input on the receiveOAS field. More detail on Figma

@shawn320 shawn320 marked this pull request as draft December 29, 2023 16:52
Copy link

@shawn320 shawn320 marked this pull request as ready for review January 2, 2024 15:44
Copy link
Collaborator

@alex-solo alex-solo left a comment

Choose a reason for hiding this comment

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

The calculations themselves seem to be working according to the new logic, nice! The tests are failing because both new fields are required as per Joi schema but the tests suite does not provide those values in any of the scenarios.

You can probably address this by setting it to zero if 'undefined' when the test suite excel sheet is being ingested. OR, since we'll need different new scenarios in the test suite, we'll need a new column for this new input. All the current tests can be auto-filled to zero or "N/A" as long as the test scripts know how to read the sheet, it's all fair game.

Take a look at excelReaderUtil.ts to see how the sheet is being processed currently. Let me know if you have any more questions!

components/ResultsPage/YourAnswers.tsx Show resolved Hide resolved
Copy link

github-actions bot commented Jan 4, 2024

Copy link

github-actions bot commented Jan 4, 2024

@shawn320 shawn320 requested review from MarcoGoC and alex-solo January 4, 2024 18:50
Copy link

github-actions bot commented Jan 4, 2024

Copy link

github-actions bot commented Jan 8, 2024

Copy link

github-actions bot commented Jan 8, 2024

Copy link

github-actions bot commented Jan 8, 2024

Copy link

github-actions bot commented Jan 9, 2024

Copy link

github-actions bot commented Jan 9, 2024

Copy link
Collaborator

@alex-solo alex-solo left a comment

Choose a reason for hiding this comment

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

already approved based on previous conversations

@shawn320 shawn320 merged commit 088ac96 into develop Jan 10, 2024
7 checks passed
@shawn320 shawn320 deleted the question-update branch January 10, 2024 14:48
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