Move PolicyQuery to permission-node

Signed-off-by: Vincenzo Scamporlino <me@vinzscam.dev>
This commit is contained in:
Vincenzo Scamporlino
2022-03-24 14:20:32 +01:00
parent b1bbb9c760
commit 2903c1fd5d
6 changed files with 38 additions and 29 deletions
+8 -4
View File
@@ -157,12 +157,16 @@ export type PermissionBase<TType extends string, TFields extends object> = {
} & TFields;
// @public
export class PermissionClient implements PermissionAuthorizer {
export class PermissionClient implements PermissionEvaluator {
constructor(options: { discovery: DiscoveryApi; config: Config });
authorize(
queries: EvaluatePermissionRequest[],
options?: AuthorizeRequestOptions,
): Promise<EvaluatePermissionResponse[]>;
requests: AuthorizePermissionRequest[],
options?: EvaluatorRequestOptions,
): Promise<AuthorizePermissionResponse[]>;
query(
queries: QueryPermissionRequest[],
options?: EvaluatorRequestOptions,
): Promise<QueryPermissionResponse[]>;
}
// @public
@@ -91,20 +91,6 @@ export type PolicyDecision =
| DefinitivePolicyDecision
| ConditionalPolicyDecision;
/**
* A query to be evaluated by the {@link PermissionPolicy}.
*
* @remarks
*
* Unlike other parts of the permission API, the policy does not accept a resource ref. This keeps
* the policy decoupled from the resource loading and condition applying logic.
*
* @public
*/
export type PolicyQuery = {
permission: Permission;
};
/**
* A condition returned with a CONDITIONAL authorization response.
*
@@ -36,7 +36,6 @@ export type {
AllOfCriteria,
AnyOfCriteria,
NotCriteria,
PolicyQuery,
} from './api';
export type { DiscoveryApi } from './discovery';
export type {