Open
Description
The anyOf
constraint on a property means that the value must match at least one of the subschemas.
My current take on this is:
- Adding a new
anyOf
schema is likely OK. From what I understand, this would not break any existing client/user expectations or invalidate any existing instances of the resource - Removing/Net-New/Changing an
anyOf
schema is breaking
Metadata
Metadata
Assignees
Labels
Denotes an issue ready for a new contributor, according to the "help wanted" guidelines.Denotes an issue that needs help from a contributor. Must meet "help wanted" guidelines.Categorizes issue or PR as related to a new feature.Important over the long term, but may not be staffed and/or may need multiple releases to complete.Indicates an issue or PR is ready to be actively worked on.