mirror of
https://github.com/bitwarden/browser
synced 2025-12-13 23:03:32 +00:00
24b84985f5
Factor general integration logic out of the forwarder code. - Integration metadata - information generalized across any integration - Rpc mechanism - first step towards applying policy to integrations is abstracting their service calls (e.g. static baseUrl) Email forwarder integrations embedded this metadata. It was extracted to begin the process of making integrations compatible with meta-systems like policy. This PR consists mostly of interfaces, which are not particularly useful on their own. Examples on how they're used can be found in the readme.
8 lines
239 B
TypeScript
8 lines
239 B
TypeScript
import { Opaque } from "type-fest";
|
|
|
|
/** Identifies a vendor integrated into bitwarden */
|
|
export type IntegrationId = Opaque<
|
|
"anonaddy" | "duckduckgo" | "fastmail" | "firefoxrelay" | "forwardemail" | "simplelogin",
|
|
"IntegrationId"
|
|
>;
|