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

8440: fix appointments contract schema #16528

Merged
merged 1 commit into from
Apr 29, 2024
Merged

Conversation

kpethtel
Copy link
Contributor

Summary

Fixes known issues with appointments index contract schema.

Related issue(s)

department-of-veterans-affairs/va-mobile-app#8440

Testing done

  • New code is covered by unit tests
  • Describe what the old behavior was prior to the change
  • Describe the steps required to verify your changes are working as expected. Exclusively stating 'Specs run' is NOT acceptable as appropriate testing
  • If this work is behind a flipper:
    • Tests need to be written for both the flipper on and flipper off scenarios. Docs.
    • What is the testing plan for rolling out the feature?

Screenshots

Note: Optional

What areas of the site does it impact?

(Describe what parts of the site are impacted andifcode touched other areas)

Acceptance criteria

  • I fixed|updated|added unit tests and integration tests for each feature (if applicable).
  • No error nor warning in the console.
  • Events are being sent to the appropriate logging solution
  • Documentation has been updated (link to documentation)
  • No sensitive information (i.e. PII/credentials/internal URLs/etc.) is captured in logging, hardcoded, or specs
  • Feature/bug has a monitor built into Datadog or Grafana (if applicable)
  • If app impacted requires authentication, did you login to a local build and verify all authenticated routes work as expected
  • I added a screenshot of the developed feature

Requested Feedback

(OPTIONAL)What should the reviewers know in addition to the above. Is there anything specific you wish the reviewer to assist with. Do you have any concerns with this PR, why?

@@ -361,7 +350,7 @@
}
},
"cc_requested_cancellation": { "type": "boolean" },
"hsrm_tast_id": { "type": "string" },
"hsrm_task_id": { "type": "string" },
Copy link
Member

Choose a reason for hiding this comment

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

Good find!

@kpethtel kpethtel merged commit 08ecdc5 into master Apr 29, 2024
23 checks passed
@kpethtel kpethtel deleted the 8440-appointments-schema branch April 29, 2024 19:16
gabezurita added a commit that referenced this pull request Apr 30, 2024
* master: (33 commits)
  [DBX-74810] Add flipper with LH BI api for 4142 (#16483)
  upadte param dig call (#16570)
  98 add code to poll average days (#16471)
  8147 claim model (#16525)
  Toxic Exposure: Save TE "Add Conditions" fields for future transformation (#16548)
  Revert "ClamAV in Containers (#15965)" (#16557)
  Dangerfile updates for db migration (#16511)
  API-35829-error_handling (#16522)
  add loggers to see what dd api call is doing in staging (#16539)
  8440: fix appointments contract schema (#16528)
  ClamAV in Containers (#15965)
  Protect against calling `.any?` on a non-array (#16547)
  BE | Ask VA Api: Refactor classes and specs (#16542)
  Added '10-10EZR' to the list of freeze schemas (#16478)
  Add prefill for 10-7959c (#16448)
  Bump shrine from 3.5.0 to 3.6.0 (#16532)
  change limit on place and location. update question number (#16537)
  Add words_to_remove for simple forms 21-0966 (#16477)
  updgrade sidekiq and super_diff (#16536)
  BE | Ask Va Api:  Update `Inquiries::Creator` `Correspondences::Creator` Error Handling (#16529)
  ...
@RachalCassity RachalCassity self-assigned this Apr 30, 2024
stevenjcumming added a commit that referenced this pull request May 1, 2024
* prefer pdftk-java with debian bookworm

* 8440: fix appointments contract schema (#16528)

* add loggers to see what dd api call is doing in staging (#16539)

* API-35829-error_handling (#16522)

* Adds error handling for new synchronous endpoint. Iterates through errors and adds them to the ecss_response on the claim. Adds to the retry? method to check the evss_response for the error key.

* Addressese PR suggestions

* REmoves error message, and uses evss_response on the claim instead.

* Adds a save rigt after updating the status on the claim

* Adds several tests

* Alters a test to more accurately test the scenario IRL

* Dangerfile updates for db migration (#16511)

* Revert "ClamAV in Containers (#15965)" (#16557)

This reverts commit 0857270.

* Toxic Exposure: Save TE "Add Conditions" fields for future transformation (#16548)

* add cause field to disabilities array

* another flipper fix

* remove debug comment

* add comment for future engs

* tests

* nil check for input_disability

* break from loop, not break from method

* 8147 claim model (#16525)

---------

Co-authored-by: Kris Pethtel <kris.pethtel@gmail.com>
Co-authored-by: s-caso <94458706+s-caso@users.noreply.github.com>
Co-authored-by: Jennica Stiehl <25069483+stiehlrod@users.noreply.github.com>
Co-authored-by: Rebecca Tolmach <10993987+rmtolmach@users.noreply.github.com>
Co-authored-by: Rachal Cassity <rachal.cassity@oddball.io>
Co-authored-by: Seth Darr <92405130+sethdarragile6@users.noreply.github.com>
Co-authored-by: Andrew Herzberg <andrew.herzberg@adhocteam.us>
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