-
Notifications
You must be signed in to change notification settings - Fork 64
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
Update release TypeScript models script #957
Comments
@sleshchenko, @JPinkney, @l0rd do we still need to keep type support for devworkspace inside of the |
@benoitf @azatsarynnyy do we use the |
yes we are using it in dashboard and in the "libraries" to enhance devfiles (theia and vscode) |
@schultzp2020 we still do need the DevWorkspace type support |
Sounds good, I'll keep them included when I add the other types. |
This issue is stale because it has been open for 90 days with no activity. Remove stale label or comment or this will be closed in 60 days. |
Which area/kind this issue is related to?
/area api
/area registry
Issue Description
Currently the workflow
release-typescript-models
releases TypeScript models only for the latest version of the devfile spec. As a consumer of devfiles, it would be nice to have TypeScript model support for all releases of the devfile spec, as well as TypeScript model support for the REST API responses.Possible solutions
swaggest/rest
. Then convert to TypeScript models by openapi-typescript.typescriptify-golang-structs
on Go source code to generate TypeScript models.Method 1 is preferred because it can be extended to easily test the API responses.
The text was updated successfully, but these errors were encountered: