You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Using the config above, the following examples would be forbidden:
147
+
148
+
- `+forbidden:marker`(all instances, including if they have attributes and values)
149
+
- `+forbidden:withAttribute:fruit=*,*`(all instances of this marker containing the attribute 'fruit')
150
+
- `+forbidden:withMultipleAttributes:fruit=*,color=*,*`(all instances of this marker containing both the 'fruit' AND 'color' attributes)
151
+
- `+forbidden:withAttributeValues:fruit={apple || banana || orange},*`(all instances of this marker containing the 'fruit' attribute where the value is set to one of 'apple', 'banana', or 'orange')
152
+
153
+
- `+forbidden:withMultipleAttributesValues:fruit={apple || banana || orange},color={red || green || blue},*`(all instances of this marker containing the 'fruit' attribute where the value is set to one of 'apple', 'banana', or 'orange' AND the 'color' attribute where the value is set to one of 'red', 'green', or 'blue')
154
+
155
+
### Fixes
156
+
157
+
Fixes are suggested to remove all markers that are forbidden.
158
+
101
159
## Integers
102
160
103
161
The `integers` linter checks for usage of unsupported integer types.
@@ -161,6 +219,14 @@ lintersConfig:
161
219
policy: Enforce | AllowStringToStringMaps | Ignore # Determines how the linter should handle maps of simple types. Defaults to AllowStringToStringMaps.
162
220
```
163
221
222
+
## NoNullable
223
+
224
+
The `nonullable` linter ensures that types and fields do not have the `nullable` marker.
225
+
226
+
### Fixes
227
+
228
+
Fixes are suggested to remove the `nullable` marker.
229
+
164
230
## Notimestamp
165
231
166
232
The `notimestamp` linter checks that the fields in the API are not named with the word 'Timestamp'.
@@ -334,10 +400,12 @@ linter will suggest adding the comment `// +kubebuilder:subresource:status` abov
334
400
335
401
The `uniquemarkers` linter ensures that types and fields do not contain more than a single definition of a marker that should only be present once.
336
402
337
-
Because this linter has no way of determining which marker definition was intended it does not suggest any fixes
403
+
Because this linter has no way of determining which marker definition was intended it does not suggest any fixes
338
404
339
405
### Configuration
406
+
340
407
It can configured to include a set of custom markers in the analysis by setting:
0 commit comments