-
Notifications
You must be signed in to change notification settings - Fork 3
align type notation for access and input #962
Copy link
Copy link
Closed
Closed
Copy link
Labels
area/documentationDocumentation relatedDocumentation relatedarea/ipceiImportant Project of Common European InterestImportant Project of Common European Interestkind/tasksmall task, normally part of feature or epicsmall task, normally part of feature or epic
Metadata
Metadata
Assignees
Labels
area/documentationDocumentation relatedDocumentation relatedarea/ipceiImportant Project of Common European InterestImportant Project of Common European Interestkind/tasksmall task, normally part of feature or epicsmall task, normally part of feature or epic
Type
Fields
Give feedbackNo fields configured for Task.
Projects
StatusShow more project fields
🍺 Done
Description
While reviewing the component authoring PR, I've noticed that our type system notation is all over the place.
Sometimes we use versioned lower case
helm/v1(for input), sometimes we use unversioned upper caseHelm(for access) (they are not the only examples). We need to converge this to one standard notation throughout our documentation.Partially related to #961.
We want to use k8s UpperCamelCase/v1 typing style as the default notation.
Update type notation in code and test examples to keep it aligned.
Done Criteria