UNPKG

@equinor/mad-core

Version:

Core library for the Mobile App Delivery team

30 lines (29 loc) 1.7 kB
export * from "./types"; export * from "./components"; export { appInsightsHasBeenInitialized, addTelemetryInitializer, Envelope, metricKeys, metricStatus, track, trackCustom, trackLongTerm, trackShortTerm, } from "@equinor/mad-insights"; export { addToast, ToastTypes, ToastType } from "@equinor/mad-toast"; export * from "./hooks"; export * from "./store"; export * from "./utils/getDefaultScreenOptionsForLoginScreen"; export { MadAccount, MadAuthenticationResult } from "@equinor/mad-auth"; import { MadAccount } from "@equinor/mad-auth"; /** * @JSDocs This export will depend on whether you have opted in to use expo-auth-session. They will function the same, but * scopes will not be applied when using expo-auth-session */ export declare const authenticateSilently: (scopes: string[]) => Promise<import("@equinor/mad-auth").MadAuthenticationResult | null>; /** * @JSDocs This export will depend on whether you have opted in to use expo-auth-session. They will function the same, but * getAcount() from expo-auth-session is not inherently async */ export declare const getAccount: () => Promise<MadAccount | null>; /** * @JSDocs This export will depend on whether you have opted in to use expo-auth-session. They will function the same, but * signOut() from expo-auth-session is not inherently async */ export declare const signOut: () => Promise<boolean>; /** * @JSDocs This export will depend on whether you have opted in to use expo-auth-session. They will function the same, but * scopes will not be applied when using expo-auth-session */ export declare const authenticateInteractively: (scopes: string[]) => Promise<import("@equinor/mad-auth").MadAuthenticationResult | null>;