Repository navigation
Machine work uint conversion #174
Description
While fixxing the linter I asked myself why we convert so much from uint to int and other way arround.
Here for example, our api wants the workers to have minsize uint32(which makes more sense, why have negative value for that), but the gardener worker has int32.
Why don't we just use the gardener worker api values like int32 which helps us remove the cast. We can manually check if it's negative and just throw an error on that case?
Already asked in gardener slack, this is probably just some issue that could be ignored, but gotta make sure before putting a ignore to the linter.
Activity
Honigeintopf commentedon Sep 13, 2024
What do you think?
https://github.com/kubernetes/community/blob/master/contributors/devel/sig-architecture/api-conventions.md#primitive-types
@Gerrit91 @vknabel
vknabel commentedon Oct 2, 2024
@Honigeintopf do you remember what we decided? If I remember correctly we decided to do nothing. In that case: can we close this issue?
Honigeintopf commentedon Oct 2, 2024
I think we went through some options on how to fix it.
If it's not possible that gardener gives us a negative value, because of int32 (maybe they do to signal sth being broken, not sure just theory), then we can put a linter ignore before it.
Imo changing it would be the better approach, might be a breaking change tho?
vknabel commentedon Oct 2, 2024
Yup, it would break almost all clients of the API (metal-cli, terraform, api-server).
The web console isn't affected as there is only
numberin JS.