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

Feature/refactor crf api requests #443

Merged
merged 7 commits into from
Jun 6, 2024

Conversation

courtneymyers
Copy link
Collaborator

Related Issues:

  • CSBAPP-352

Main Changes:

Refactor the 2022 CRF API logic into common functions that will support both the 2022 and 2023 CRF forms (similar to what was done for the FRF and PRF forms). No functional change for the 2022 CRFs – just preparing wrapper app to support eventual 2023 CRFs.

Steps To Test:

  1. Navigate to the dashboard.
  2. Ensure at least one 2022 PRF has been selected (BAP "Accepted" status).
  3. Click "New Close Out" button – ensure a new close out form is created.
  4. Click "Next" on the form, and ensure the form is updated.
  5. Return to the user dashboard.
  6. Click "Edit" beside the newly created 2023 CRF, and ensure it loads.
  7. Click "Next" again on the form (possibly changing form field values as needed), and ensure form is updated.

@courtneymyers
Copy link
Collaborator Author

IMPORTANT: Not to be merged until after v5 is released, as this is part of the v6 wrapper release.

@courtneymyers courtneymyers merged commit cbf0c65 into develop Jun 6, 2024
1 check passed
@courtneymyers courtneymyers deleted the feature/refactor-crf-api-requests branch June 6, 2024 15:47
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.

1 participant