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

Ap 4503 correction to ineligible result #5982

Merged
merged 6 commits into from
Nov 21, 2023

Conversation

kmahern
Copy link
Contributor

@kmahern kmahern commented Nov 13, 2023

What

Link to story

I have added code to handle the scenario where CFE returns 'ineligible' for multiple categories out of gross income, disposable income and capital and added a 'fake' CFE result to test this scenario, however, in practice this is not currently happening, see https://dsdmoj.atlassian.net/browse/AP-4503?focusedCommentId=342986 and https://github.com/ministryofjustice/laa-apply-for-legal-aid/pull/5982/files#r1392418804. This has been added as it is the desired way for CFE to work that is shown in the designs for this ticket but I am not sure if it is the best/correct approach?

Checklist

Before you ask people to review this PR:

  • Tests and rubocop should be passing: bundle exec rake
  • Github should not be reporting conflicts; you should have recently run git rebase main.
  • There should be no unnecessary whitespace changes. These make diffs harder to read and conflicts more likely.
  • The PR description should say what you changed and why, with a link to the JIRA story.
  • You should have looked at the diff against main and ensured that nothing unexpected is included in your changes.
  • You should have checked that the commit messages say why the change was made.

@kmahern kmahern force-pushed the ap-4503-correction-to-ineligible-result branch 12 times, most recently from 24844b3 to 7bd3889 Compare November 14, 2023 10:01
result
end

# This result has has been faked, to cover an example where CFE returns 'ineligible'
Copy link
Contributor Author

@kmahern kmahern Nov 14, 2023

Choose a reason for hiding this comment

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

Is this approach best/correct?

@kmahern kmahern marked this pull request as ready for review November 14, 2023 11:42
@kmahern kmahern requested a review from a team as a code owner November 14, 2023 11:42
Copy link
Contributor

@jsugarman jsugarman left a comment

Choose a reason for hiding this comment

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

looking good, some comments as we discussed.

app/helpers/ineligible_reasons_helper.rb Outdated Show resolved Hide resolved
app/helpers/ineligible_reasons_helper.rb Outdated Show resolved Hide resolved
app/helpers/ineligible_reasons_helper.rb Outdated Show resolved Hide resolved
app/helpers/ineligible_reasons_helper.rb Outdated Show resolved Hide resolved
@kmahern kmahern force-pushed the ap-4503-correction-to-ineligible-result branch from 6b535a1 to d132944 Compare November 15, 2023 15:02
# for more than one proceeding category, which it appears is currently not possible.
# Currently if an applicant is ineligible for disposable income and capital,
# CFE returns the disposable income result for proceedings as 'ineligible',
# but the capital result for proceedings as 'pending'.
Copy link
Contributor

Choose a reason for hiding this comment

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

You could add that this is due to a current "shortcut" in CFE that may be removed in the future - see LEP-349

Copy link
Contributor

@jsugarman jsugarman left a comment

Choose a reason for hiding this comment

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

👍 A couple of test nits which I personally have been trying to address whenever i see them, plus you could add reference https://dsdmoj.atlassian.net/browse/LEP-349 in the code comment you added on the fake result payload.

@kmahern kmahern force-pushed the ap-4503-correction-to-ineligible-result branch from ac1de22 to 92a2518 Compare November 16, 2023 15:57
@jsugarman jsugarman added approved Approved by code reviewers UAT labels Nov 16, 2023
@kmahern kmahern force-pushed the ap-4503-correction-to-ineligible-result branch from 92a2518 to 5ca265a Compare November 21, 2023 10:05
Copy link

Kudos, SonarCloud Quality Gate passed!    Quality Gate passed

Bug A 0 Bugs
Vulnerability A 0 Vulnerabilities
Security Hotspot A 0 Security Hotspots
Code Smell A 0 Code Smells

No Coverage information No Coverage information
0.0% 0.0% Duplication

@kmahern kmahern merged commit 5059908 into main Nov 21, 2023
7 checks passed
@kmahern kmahern deleted the ap-4503-correction-to-ineligible-result branch November 21, 2023 10:16
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
approved Approved by code reviewers UAT
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants