-
Couldn't load subscription status.
- Fork 3
Closed
Description
- Use the OpenAPI spec to generate an initial standalone .Net core client
- Ensure the client can be easily updated as the spec changes
- Ensure the client has solid test automation
- Ensure the client has basic documentation for usage instructions
- (Optional) Publish the client to Nuget (should probably be its own card)
Open questions:
- Should the client live in its own repo, or be a subdirectory in the OpenAPI spec project?
- How do the generated clients look? Should we consider building custom generator logic / templates to ensure a smoother transition to the new clients from our current SDK (like Bitmovin describes doing in their blog post - Section 2)