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

FYST-843 Implement MD502R XML/PDF Part 2: disability, retirement/pension income #5489

Conversation

arinchoi03
Copy link
Contributor

@arinchoi03 arinchoi03 commented Jan 30, 2025

Link to pivotal/JIRA issue

Is PM acceptance required?

  • Yes - don't merge until JIRA issue is accepted!

Reminder: merge main into this branch and get green tests before merging to main

What was done?

  • Added disability-related logic to xml/pdf
  • Added lines 1a, 1b, 7a, 7b, 8, 10a, 10b to xml/pdf
    • line 10a & 10b: stubbed out for later implementation
  • Implemented methods to pull out 1099Rs for a specific filer depending on the SSN match & how to pull followup amounts for summing

How to test?

  • Describe the testing approach taken to verify the changes, including:
    • Unit/manual tests
    • Test data used: dorothy_mfj_1099_r

Screenshots (for visual changes)

Screenshot 2025-01-31 at 11 12 58 AM Screenshot 2025-01-31 at 11 16 27 AM

Copy link

Heroku app: https://gyr-review-app-5489-78676a7367ab.herokuapp.com/
View logs: heroku logs --app gyr-review-app-5489 (optionally add --tail)

@arinchoi03 arinchoi03 marked this pull request as draft January 30, 2025 21:33
@arinchoi03 arinchoi03 changed the title FYST-843 FYST 1614 Implement MD502R XML/PDF Part 2: Everything else FYST-843 Implement MD502R XML/PDF Part 2: Everything else Jan 30, 2025
@arinchoi03 arinchoi03 marked this pull request as ready for review January 31, 2025 19:08
@arinchoi03 arinchoi03 changed the title FYST-843 Implement MD502R XML/PDF Part 2: Everything else FYST-843 Implement MD502R XML/PDF Part 2: disability, retirement/pension income Jan 31, 2025
end
end
end

Copy link
Contributor Author

Choose a reason for hiding this comment

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

these methods were added to the intake b/c other calculators will need this logic as well

if state_file_1099_r.state_specific_followup&.send(followup_type)
state_file_1099_r.taxable_amount&.round
else
0
Copy link
Contributor Author

@arinchoi03 arinchoi03 Jan 31, 2025

Choose a reason for hiding this comment

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

there was no strict requirement that if a 1099r followup was not present (or if it didn't match the followup_type for this 1099R) that it should return nilvs0`.

Since handling nil for summation (downstream too, not just in this block) can be tricky, chose to not go down this route unless needed for simplicity

Copy link
Contributor

@anisharamnani anisharamnani left a comment

Choose a reason for hiding this comment

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

Thanks Arin for tackling this work! 😸 Since we reviewed this on Friday, I don't have any comments or requests for changes.

@arinchoi03 arinchoi03 merged commit d52b789 into main Feb 4, 2025
7 checks passed
@arinchoi03 arinchoi03 deleted the FYST-843-md-implement-form-502-r-retirement-income-xml-pdf-part-2 branch February 4, 2025 17:35
end
end

def sum_1099_r_followup_type_for_filer(filer_1099_rs, followup_type)
Copy link
Contributor

Choose a reason for hiding this comment

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

do we need to pass in the filer_1099_rs here? or instead should we pass in primary or spouse?

Copy link
Contributor Author

Choose a reason for hiding this comment

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

ooh we can pass in the primary_or_spouse here and call the filer_1099_rs method from within this method!

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