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
pass.Reportf(field.Pos(), "field %s.%s with marker +%s requires at least one of the following markers, but none were found: %s", structName, fieldName, rule.Identifier, strings.Join(dependents, ", "))
121
+
pass.Reportf(field.Pos(), "field %s with marker +%s requires at least one of the following markers, but none were found: %s", qualifiedFieldName, rule.Identifier, strings.Join(dependents, ", "))
Copy file name to clipboardExpand all lines: pkg/analysis/dependenttags/doc.go
+6-6Lines changed: 6 additions & 6 deletions
Original file line number
Diff line number
Diff line change
@@ -21,30 +21,30 @@ limitations under the License.
21
21
// a set of other markers (dependent tags) are also present. This is useful for enforcing API
22
22
// contracts where certain markers imply the presence of others.
23
23
//
24
-
// For example, a field marked with `+k-8s:unionMember` must also be marked with `+k8s:optional`.
24
+
// For example, a field marked with `+k8s:unionMember` must also be marked with `+k8s:optional`.
25
25
//
26
26
// # Configuration
27
27
//
28
28
// The linter is configured with a list of rules. Each rule specifies an identifier marker and a list of
29
29
// dependent markers. The `type` field is required and specifies how to interpret the dependents list:
30
-
// - `all`: all dependent markers are required.
31
-
// - `any`: at least one of the dependent markers is required.
30
+
// - `All`: all dependent markers are required.
31
+
// - `Any`: at least one of the dependent markers is required.
32
32
//
33
33
// This linter only checks for the presence or absence of markers; it does not inspect or enforce specific values within those markers. It also does not provide automatic fixes.
0 commit comments