Member Junction
    Preparing search index...

    Implementation of the Expo push-notification provider for MemberJunction's Communication framework. Sends mobile push notifications to Expo push tokens via the Expo Push API using a simple HTTPS POST (no SDK dependency).

    Push notifications are a fire-and-forget, send-only channel. Consequently this provider implements only SendSingleMessage; the mailbox-style operations (GetMessages, ForwardMessage, ReplyToMessage, CreateDraft) return a "not supported" result, consistent with the base-class contract.

    Hierarchy (View Summary)

    Index

    Constructors

    Accessors

    • get ProviderName(): string

      Returns the name of this provider for use in error messages. Override in subclasses to provide a more descriptive name.

      Returns string

    • get SupportsPush(): boolean

      Convenience gate: true when this provider supports inbound push in ANY form (subscription-managed or inbound-parse), false otherwise. Lets callers cleanly short-circuit — if (provider.SupportsPush) { ... } — instead of probing individual operations.

      Derived from GetSubscriptionCapabilities so it stays in lockstep with actual capability: providers that support push return capabilities and thereby report SupportsPush === true for free; providers that don't return undefined and report false. Subclasses normally do NOT override this — override GetSubscriptionCapabilities instead.

      Returns boolean

    Methods

    • Returns this provider's subscription capabilities, or undefined when subscriptions are not supported. Consumers use this to schedule renewals and validate change types generically. Override in subclasses that support subscriptions.

      INVARIANT: returning a defined value here REQUIRES the four subscription operations to appear in getSupportedOperations.

      Returns SubscriptionCapabilities

      SubscriptionCapabilities when supported, otherwise undefined