From 0b0942d1922459b96b93896db14a19b3f6e6c8cf Mon Sep 17 00:00:00 2001 From: Tom Foster Date: Fri, 14 Feb 2025 15:00:53 +0000 Subject: [PATCH] Clarify capability lists should support wildcards --- data/api/client-server/capabilities.yaml | 14 ++++++++------ 1 file changed, 8 insertions(+), 6 deletions(-) diff --git a/data/api/client-server/capabilities.yaml b/data/api/client-server/capabilities.yaml index b340a517..9e4810f1 100644 --- a/data/api/client-server/capabilities.yaml +++ b/data/api/client-server/capabilities.yaml @@ -154,13 +154,10 @@ components: type: object title: ProfileFieldsCapability properties: - enabled: - type: boolean - description: True if the user can set or modify any extended profile fields, false otherwise. - example: true allowed: type: array - description: List of allowed custom profile field keys. This takes precedence over disallowed if both are provided. + description: List of allowed custom profile field keys, + supporting `glob.*` wildcard format. Takes precedence over disallowed if both are provided. items: type: string example: @@ -168,10 +165,15 @@ components: - "org.example.job_title" disallowed: type: array - description: List of disallowed custom profile field keys. Ignored if allowed is provided. + description: List of disallowed custom profile field keys, + supporting `glob.*` wildcard format. Ignored if allowed is provided. items: type: string example: - "org.example.secret_field" + enabled: + type: boolean + description: True if the user can set or modify any extended profile fields, false otherwise. + example: true required: - enabled