Merge pull request #1765 from ably/wildcard-capability

types/capability: allow wildcard capability when presented in object form, add privileged-headers capability

ably.d.ts

@@ -683,7 +683,9 @@ export type capabilityOp =
   | 'stats'
   | 'channel-metadata'
   | 'push-subscribe'
-  | 'push-admin';
+  | 'push-admin'
+  | 'privileged-headers';
+
 /**
  * Capabilities which are available for use within {@link TokenParams}.
  */
@@ -698,7 +700,7 @@ export interface TokenParams {
    *
    * @defaultValue `'{"*":["*"]}'`
    */
-  capability?: { [key: string]: capabilityOp[] } | string;
+  capability?: { [key: string]: capabilityOp[] | ['*'] } | string;
   /**
    * A client ID, used for identifying this client when publishing messages or for presence purposes. The `clientId` can be any non-empty string, except it cannot contain a `*`. This option is primarily intended to be used in situations where the library is instantiated with a key. Note that a `clientId` may also be implicit in a token used to instantiate the library. An error is raised if a `clientId` specified here conflicts with the `clientId` implicit in the token. Find out more about [identified clients](https://ably.com/docs/core-features/authentication#identified-clients).
    */