Fix capability creation via public API (#220)

Ref #216: the public API seems to now complain when passing in
`capabilities`, but the field is still required when using the private
API.

Co-authored-by: sfusco <slf@stevenfusco.com>
This commit is contained in:
Kabir Oberai
2026-05-16 20:04:51 -04:00
committed by GitHub
Unverified
parent c65d45ba60
commit 8edb54fb71
5 changed files with 326 additions and 477 deletions
+1 -2
View File
@@ -65,7 +65,7 @@ function openAll(schema, path = []) {
function patch(schema) {
const schemas = schema.components.schemas;
// this field is required when using the private Xcode API
// this field is required iff using the private Xcode API
update(schemas.BundleIdCapabilityCreateRequest.properties.data.properties.relationships, {
properties: {
capability: {
@@ -86,7 +86,6 @@ function patch(schema) {
required: ['data'],
}
},
required: ['capability'],
})
// we don't use this but it triggers a deprecation warning. see: