You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
As a developer working on tooling that supports the OSCAL REST API specification, I want to have a standard API client so that I can more easily make requests to the API following the specification
Acceptance Criteria
An API client is available in at least TypeScript and is usable within the OSCAL React Library
Proposed Solution
No response
Additional Notes
Swagger (and other tooling) allow automatically generating clients from the OpenAPI specification. This may be sufficient; however, we may also consider hand-rolling (but should be very careful about doing so).
If the client is automatically generated, we should have tooling to automatically update the generated client from the specification.
Implementation
I can (or plan to) submit a pull request to implement this
Implementing this may result in a breaking change
The text was updated successfully, but these errors were encountered:
@kylelaker Can you revise this ticket to reflect an client for the Transaction API instead of the REST API?
Or close it an open a new issue for that purpose?
Description
As a developer working on tooling that supports the OSCAL REST API specification, I want to have a standard API client so that I can more easily make requests to the API following the specification
Acceptance Criteria
Proposed Solution
No response
Additional Notes
Swagger (and other tooling) allow automatically generating clients from the OpenAPI specification. This may be sufficient; however, we may also consider hand-rolling (but should be very careful about doing so).
If the client is automatically generated, we should have tooling to automatically update the generated client from the specification.
Implementation
The text was updated successfully, but these errors were encountered: