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

API-26923 Update description wording for appeals APIs #12850

Merged
merged 0 commits into from
Jun 2, 2023

Conversation

caseywilliams
Copy link
Contributor

Summary

  • Updates descriptions of segmented APIs based on the google doc linked in API-26923

Related issue(s)

Testing done

  • Regenerated all OAS json

What areas of the site does it impact?

  • Updates wording in descriptions of Appeals APIs in the dev portal

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

@caseywilliams caseywilliams added Lighthouse lighthouse appeals Lighthouse API appeals banana-peels Lighthouse Banana Peels Team labels May 31, 2023
@caseywilliams caseywilliams requested review from a team as code owners May 31, 2023 20:57
@caseywilliams caseywilliams force-pushed the API-26923/oas-updates branch from f8853bd to 766d9aa Compare May 31, 2023 20:57
@va-vsp-bot va-vsp-bot requested a deployment to API-26923/oas-updates/main/main May 31, 2023 20:57 In progress
@va-vfs-bot va-vfs-bot temporarily deployed to API-26923/oas-updates/main/main May 31, 2023 20:59 Inactive
* [Supplemental Claims API](https://developer.va.gov/explore/appeals/docs/supplemental_claims)
* [Higher-Level Reviews API](https://developer.va.gov/explore/appeals/docs/higher_level_reviews)
* [Notice of Disagreements API](https://developer.va.gov/explore/appeals/docs/notice_of_disagreements)
* [Supplemental Claims API](https://developer.va.gov/explore/appeals/docs/supplemental_claims)
Copy link
Contributor Author

Choose a reason for hiding this comment

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

This file already had the line about CCG access that's added to all the other docs in this PR, but I updated the indentation here so that the dev and prod versions can be more easily compared at a glance (they are almost identical)

@@ -23,7 +23,7 @@ The authentication model for the Appeals Status API uses OAuth 2.0/OpenID Connec
* [Authorization code flow](https://dev-developer.va.gov/explore/authorization/docs/authorization-code?api=appeals)
* [Client credentials grant](https://dev-developer.va.gov/explore/authorization/docs/client-credentials?api=appeals) (restricted access)

**Important:** To get production access using client credentials grant, you must either work for VA or have specific VA agreements in place. If you have questions, [contact us](https://developer.va.gov/support/contact-us).
**Important:** To get production access using client credentials grant, you must either work for VA or have specific VA agreements in place. If you have questions, [contact us](https://dev-developer.va.gov/support/contact-us).
Copy link
Contributor Author

Choose a reason for hiding this comment

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

This text was already here but I realized it wasn't using the dev-developer hostname like other docs for dev

@@ -35,5 +37,3 @@ Test submissions do not progress through the same statuses as the production env

#### Status Caching
Due to system limitations, status attribute data for the GET `/forms/200996/{uuid}` endpoint is cached for 1 hour. The updated_at field indicates the last time the status for a given GUID was updated.

### [Terms of service](https://dev-developer.va.gov/terms-of-service)
Copy link
Contributor Author

Choose a reason for hiding this comment

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

The "Terms of service" links in these updates are removed because there's already a ToS link in the OAS JSON's data - these links in the descriptions are duplicative

@caseywilliams caseywilliams force-pushed the API-26923/oas-updates branch from 766d9aa to 93d6014 Compare May 31, 2023 21:26
@va-vsp-bot va-vsp-bot requested a deployment to API-26923/oas-updates/main/main May 31, 2023 21:27 In progress
@va-vfs-bot va-vfs-bot temporarily deployed to API-26923/oas-updates/main/main May 31, 2023 21:28 Inactive
@caseywilliams caseywilliams force-pushed the API-26923/oas-updates branch from 93d6014 to eacdfa3 Compare June 1, 2023 00:55
@va-vsp-bot va-vsp-bot requested a deployment to API-26923/oas-updates/main/main June 1, 2023 00:56 In progress
@va-vfs-bot va-vfs-bot temporarily deployed to API-26923/oas-updates/main/main June 1, 2023 00:56 Inactive
@caseywilliams caseywilliams force-pushed the API-26923/oas-updates branch from eacdfa3 to a9e7fd5 Compare June 1, 2023 16:31
@va-vsp-bot va-vsp-bot requested a deployment to API-26923/oas-updates/main/main June 1, 2023 16:31 In progress
@va-vfs-bot va-vfs-bot temporarily deployed to API-26923/oas-updates/main/main June 1, 2023 16:32 Inactive
Copy link
Contributor

@kristen-brown kristen-brown left a comment

Choose a reason for hiding this comment

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

LGTM! 🎉

@caseywilliams caseywilliams merged commit 0cecb24 into master Jun 2, 2023
@caseywilliams caseywilliams deleted the API-26923/oas-updates branch June 2, 2023 16:14
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
appeals Lighthouse API appeals banana-peels Lighthouse Banana Peels Team Lighthouse lighthouse
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants