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

Create an API subpage with embedded swagger React component #58

Open
9 tasks
j-tafoya opened this issue Jan 21, 2022 · 0 comments
Open
9 tasks

Create an API subpage with embedded swagger React component #58

j-tafoya opened this issue Jan 21, 2022 · 0 comments
Labels
API docs subpage This component applies to the API docs subpage

Comments

@j-tafoya
Copy link
Collaborator

Definition of Ready

  • Does this meet the INVEST criteria?
  • Does this have a clearly defined user?
  • Does this have acceptance criteria?
  • Does this have sufficient context for the specific functionality being developed (design, business rules, etc.)

User Story

As a user (developer)
I want to see the swagger page for an API with a description and additional info
So that I can use endpoints in my own work/project

Acceptance Criteria

Given any CAM API
When a user visits an API subpage
Then a description and any potential additional information should display at the top with the embedded swagger page below

Given a generic API subpage component
When a developer is creating the API docs subpage
Then they should be able to dynamically create as many API subpages as there are APIs

Development Notes

See the wireframes for reference. This component should be generic enough to create any number of subpages without significant effort to create new pages.

Testing

Test Description

Verify the page loads appropriately with the swagger component and responds to mobile and desktop sizes

Assumptions and Pre-Conditions

n/a

Test Data

Given any OpenAPI spec and description text, this component should be able to render the page given props.

Steps to be Executed

  1. Supply a description/ any additional info and an OpenAPI spec url to the component
  2. Test that the component renders the info appropriately and the swagger page is interactable
  3. Verify that the page responds to mobile and desktop sizes

Definition of Done

  • Have all Acceptance Criteria been agreed to and validated by the scrum team?
  • Has the code been unit tested and peer reviewed?
  • Have the functional tests been executed?
  • Have all defects been reviewed and dispositioned, resolved, or deferred?
  • Is the user story ready to be deployed to the test/staging environments?
@j-tafoya j-tafoya added the API docs subpage This component applies to the API docs subpage label Jan 21, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
API docs subpage This component applies to the API docs subpage
Projects
Archived in project
Development

No branches or pull requests

1 participant