backstage / backstage/backstage
refactor(kubernetes-frontend): use kubernetes-models types instead of kubernetes/client-node types
- Dominant language
- TypeScript
- Stars
- 34.4k
- Forks
- 7.6k
- Avg merge
- 8h 57m
- Merged PRs (30d)
- 50
Description
The types in [kubernetes/client-node](https://github.com/kubernetes-client/javascript) are not a great fit for the frontend since:
1. The library is designed to be used only server side and thus some functionality doesn't work
2. We transfer the data from the backend to the frontend and so some types don't match the expected types in kubernetes/client-node (basically all dates, they are strings but the library expects them to be JS Date)
Contributor guide
Research direction
Start by locating frontend imports and uses of kubernetes/client-node types, then compare them with the data transferred from the backend and the kubernetes-models types. Done means the frontend no longer depends on kubernetes/client-node types and its transferred date strings remain correctly represented.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- kubernetes, typescript
- Domain
- frontend
- Issue type
- Refactor
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100