@duckduckgo/content-scope-scripts
    Preparing search index...

    The data bundle that accompanies an action. Which key an action reads is chosen by its dataSource; when an action omits dataSource the executor applies a fallback default (extract/navigate/click -> userProfile, fillForm -> extractedProfile, solveCaptcha -> token). An action may set dataSource explicitly to read a different bundle (e.g. a fillForm reading userProfile). fetchedEmail/emailData are also supported, for email-confirmation flows.

    interface ActionData {
        emailData?: { [k: string]: string };
        extractedProfile?: ExtractedProfile;
        fetchedEmail?: { email?: string; [k: string]: unknown };
        token?: string;
        userProfile?: UserProfile;
        [k: string]: unknown;
    }

    Indexable

    • [k: string]: unknown
    Index

    Properties

    emailData?: { [k: string]: string }

    email-derived values such as a verification code (read when an action sets dataSource: emailData)

    extractedProfile?: ExtractedProfile
    fetchedEmail?: { email?: string; [k: string]: unknown }

    a fetched email address (read when an action sets dataSource: fetchedEmail)

    token?: string

    a solved captcha token (used by solveCaptcha)

    userProfile?: UserProfile