Reconcile string enums with generated union types

[wilsonianb]

• feat(backend): request grant to query incoming payment receiver  #779 (comment)

auth and backend have been handling grant access types and actions as string enums:

rafiki/packages/auth/src/access/types.ts

Lines 1 to 13 in cbbc416

	export enum AccessType {
	Account = 'account',
	IncomingPayment = 'incoming-payment',
	OutgoingPayment = 'outgoing-payment',
	Quote = 'quote'
	}
	export enum Action {
	Create = 'create',
	Read = 'read',
	List = 'list',
	Complete = 'complete'
	}

rafiki/packages/backend/src/open_payments/auth/grant.ts

Lines 14 to 27 in cbbc416

	export enum AccessType {
	IncomingPayment = 'incoming-payment',
	OutgoingPayment = 'outgoing-payment',
	Quote = 'quote'
	}
	export enum AccessAction {
	Create = 'create',
	Read = 'read',
	ReadAll = 'read-all',
	Complete = 'complete',
	List = 'list',
	ListAll = 'list-all'
	}

open-payments's generated types define distinct access typescript types for individual access types (incoming/outgoing payment, quote):

rafiki/packages/open-payments/src/generated/auth-server-types.ts

Lines 245 to 287 in cbbc416

	"access-item":
	| external["https://raw.githubusercontent.com/interledger/open-payments/b363d33038fe789e5388f04f80ddd06a4fa97093/openapi/schemas.yaml"]["components"]["schemas"]["access-incoming"]
	| external["https://raw.githubusercontent.com/interledger/open-payments/b363d33038fe789e5388f04f80ddd06a4fa97093/openapi/schemas.yaml"]["components"]["schemas"]["access-outgoing"]
	| external["https://raw.githubusercontent.com/interledger/open-payments/b363d33038fe789e5388f04f80ddd06a4fa97093/openapi/schemas.yaml"]["components"]["schemas"]["access-quote"];
	/** access-incoming */
	"access-incoming": {
	/** @description The type of resource request as a string. This field defines which other fields are allowed in the request object. */
	type: "incoming-payment";
	/** @description The types of actions the client instance will take at the RS as an array of strings. */
	actions: (
	| "create"
	| "complete"
	| "read"
	| "read-all"
	| "list"
	| "list-all"
	)[];
	/**
	* Format: uri
	* @description A string identifier indicating a specific resource at the RS.
	*/
	identifier?: string;
	};
	/** access-outgoing */
	"access-outgoing": {
	/** @description The type of resource request as a string. This field defines which other fields are allowed in the request object. */
	type: "outgoing-payment";
	/** @description The types of actions the client instance will take at the RS as an array of strings. */
	actions: ("create" | "read" | "read-all" | "list" | "list-all")[];
	/**
	* Format: uri
	* @description A string identifier indicating a specific resource at the RS.
	*/
	identifier: string;
	limits?: external["https://raw.githubusercontent.com/interledger/open-payments/b363d33038fe789e5388f04f80ddd06a4fa97093/openapi/schemas.yaml"]["components"]["schemas"]["limits-outgoing"];
	};
	/** access-quote */
	"access-quote": {
	/** @description The type of resource request as a string. This field defines which other fields are allowed in the request object. */
	type: "quote";
	/** @description The types of actions the client instance will take at the RS as an array of strings. */
	actions: ("create" | "read" | "read-all")[];
	};

As is they do not play nicely with each other.
One possible solution is to ditch the string enums in favor of the generated types.
In the future it may be possible to at least generate the actions as enums:

• [Feature request] Generate Enums AND Union types openapi-ts/openapi-typescript#941