Extend maxlength linter to support kubernetes declarative validation markers #875
itzPranshulAnnotations
10 errors and 1 warning
|
Test
unexpected diagnostic: field DVMaxLength.ArrayWithDVMaxItems must have a maximum items, add kubebuilder:validation:MaxItems marker
|
|
Test
unexpected diagnostic: field DVMaxLength.ByteSliceWithDVMaxBytes must have a maximum length, add kubebuilder:validation:MaxLength marker
|
|
Test
unexpected diagnostic: field DVMaxLength.StringWithDVMaxLength must have a maximum length, add kubebuilder:validation:MaxLength marker
|
|
Test
diagnostic "field DVMaxLengthWithAliases.AliasArrayWithoutMaxItems array element type StringAliasDVMaxLength must have a maximum length, add kubebuilder:validation:MaxLength marker" does not match pattern `field DVMaxLengthWithAliases.AliasArrayWithoutMaxItems must have a maximum items, add kubebuilder:validation:MaxItems marker`
|
|
Test
unexpected diagnostic: field DVMaxLengthWithAliases.AliasArrayWithMaxItems array element type StringAliasDVMaxLength must have a maximum length, add kubebuilder:validation:MaxLength marker
|
|
Test
unexpected diagnostic: field DVMaxLength.DVEnumString must have a maximum length, add kubebuilder:validation:MaxLength marker
|
|
Test
unexpected diagnostic: field DVMaxLength.MapWithDVMaxProperties must have a maximum properties, add kubebuilder:validation:MaxProperties marker
|
|
Test
unexpected diagnostic: field DVMaxLength.ArrayWithDVMaxItems must have a maximum items, add kubebuilder:validation:MaxItems marker
|
|
Test
unexpected diagnostic: field DVMaxLength.ByteSliceWithDVMaxBytes must have a maximum length, add kubebuilder:validation:MaxLength marker
|
|
Test
unexpected diagnostic: field DVMaxLength.StringWithDVMaxLength must have a maximum length, add kubebuilder:validation:MaxLength marker
|
|
Test
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@34e114876b0b11c390a56381ad16ebd13914f8d5, actions/setup-go@40f1582b2485089dde7abd97c1529aa768e1baff. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|