internal/mcp: treat zero struct fields generously
Validating a struct is ambiguous, because a zero field could be considered missing or present. Interpret a zero optional struct field in whichever way results in success. Change-Id: I6a9474e6f6558d2a8522bc5ba0451967367e467d Reviewed-on: https://go-review.googlesource.com/c/tools/+/675956 Reviewed-by: Alan Donovan <adonovan@google.com> LUCI-TryBot-Result: Go LUCI <golang-scoped@luci-project-accounts.iam.gserviceaccount.com>
This commit is contained in:
parent
b7d1ec0604
commit
a08732fd0a
1 changed files with 122 additions and 26 deletions
|
|
@ -181,6 +181,15 @@ func (s *Schema) checkLocal(report func(error)) {
|
|||
s.patternProperties[re] = subschema
|
||||
}
|
||||
}
|
||||
|
||||
// Build a set of required properties, to avoid quadratic behavior when validating
|
||||
// a struct.
|
||||
if len(s.Required) > 0 {
|
||||
s.isRequired = map[string]bool{}
|
||||
for _, r := range s.Required {
|
||||
s.isRequired[r] = true
|
||||
}
|
||||
}
|
||||
}
|
||||
|
||||
// resolveURIs resolves the ids and anchors in all the schemas of root, relative
|
||||
|
|
|
|||
Loading…
Reference in a new issue