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

New results #1096

Closed
wants to merge 13 commits into from
Closed

New results #1096

wants to merge 13 commits into from

Conversation

Maxim-Lam
Copy link
Contributor

@Maxim-Lam Maxim-Lam commented Jul 5, 2024

AB#145598 - New Results

Description

  • Mega PR for the new results.

List of proposed changes:

  • move dropdowns from the next steps into the summary section
  • combine estimates into when user and partner are eligible (at this time, next eligible year and last eligible year)
  • change summary estimate messages
  • change next step texts
  • small refactor to how the result page format

What to test for/How to test

  • Play around and make sure that nothing breaks the code under any scenario. See if there are any glaring issues, typos or coding standards discrepancy.
  • Would need a dynamic link so that team can start QAing ASAP

Additional Notes

Copy link

github-actions bot commented Jul 5, 2024

Copy link

github-actions bot commented Jul 5, 2024

@Maxim-Lam Maxim-Lam requested review from MarcoGoC and alex-solo July 9, 2024 10:16
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.

Looking great Max, well done! This was a lot of work here. I am still reviewing but the only things I am seeing now are:

  • potentially padding could be larger in places? (haven't consulted the Figma designs myself). Specifically, referring to the arrows on dropdowns being close to their border and numbers in the table seem cramped.
Screenshot 2024-07-10 at 09 17 26 - This one here, seems like wrong messaging. For reference, the user was 67.5 and partner 61.5 years old and I am getting the message: "until the age 62..." for partner which doesn't seem right. image

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.

awesome overall, good organization of components, just left a few more comments

import { WebTranslations } from '../../i18n/web'
import { MaritalStatus } from '../../utils/api/definitions/enums'
import { useTranslation } from '../Hooks'

Copy link
Collaborator

Choose a reason for hiding this comment

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

Broken for me:

image

components/ResultsPage/Modal.tsx Outdated Show resolved Hide resolved
/*
returns benefit name with from/de and proper article. ... french nuances.
*/

const openModal = (e) => {
setModalPosition({ x: e.clientX, y: e.clientY })
Copy link
Collaborator

Choose a reason for hiding this comment

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

See comment in the Modal component as well. Don't think tracking position is necessary.

}> = ({ partner, resultObject, resultArray, age, maritalStatus }) => {
const tsln = useTranslation<WebTranslations>()
const apiTrans = getTranslations(tsln._language)
age = Math.round(age)
Copy link
Collaborator

Choose a reason for hiding this comment

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

passed in props should be immutable. Instead of reassigning, should assign to a local var, "roundedAge" maybe?


const eligibleAmt = numberToStringCurrency(eligibleTotalAmount, language)

const arrayofben = benefitResultArray
Copy link
Collaborator

Choose a reason for hiding this comment

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

small comment, just for consistency: "arrayOfBen"

}

//BUILD THE SUMMARY STRINGS FOR EACH BENFIT
const buildSummaryString = () => {
Copy link
Collaborator

Choose a reason for hiding this comment

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

This function is a bit difficult to read with the nested ifs but should be alright. Could try to refactor with an LLM potentially?

Copy link

Copy link

github-actions bot commented Oct 8, 2024

Copy link

github-actions bot commented Oct 8, 2024

Copy link

github-actions bot commented Oct 9, 2024

Copy link

@Maxim-Lam Maxim-Lam closed this Dec 12, 2024
@Maxim-Lam
Copy link
Contributor Author

closed to open new PR with dynamic link

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.

2 participants