@fanfare-io/fanfare-sdk-solid 0.20.0 → 0.21.0

package/README.md

@@ -38,6 +38,8 @@ npm install @fanfare-io/fanfare-sdk-core @fanfare-io/fanfare-sdk-solid solid-js
 
 Solid applications can use `FanfareProvider`, `ExperienceWidget`, and `useExperienceJourney` directly: the same journey contract as the React adapter, with Solid reactivity.
 
+`auto-start` (`autoStart` in Solid) routes the journey on mount; entering is a separate matter. A queue, draw or timed release the merchant set to enter on arrival needs no Enter click: the SDK enters the consumer inside the routing operation that lands on it, and the widget shows a joining wait — no Enter control — until they have their place, then the participating screen. If the entry is turned down, the widget falls back to the ordinary Enter screen with the refusal beside it. A host that wants every entry to stay an explicit press passes `automaticEntry={false}` to the Solid `ExperienceWidget`, the same `automaticEntry` option to `useExperienceJourney`, or `automatic-entry="false"` on `<fanfare-experience-widget>`; all three reach the ready view's `start`, and omitting it keeps the SDK default of entering on arrival. The contract is in the core package's `docs/UPGRADING-automatic-entry.md` in the SDK repository.
+
 `slots` override targeted states while keeping the default widget flow. `children` receives `{ journey, view, snapshot, error, start, isStarting }` when you want to render the full state yourself. Solid `ExperienceWidget` accepts both `class` and `className`.
 
 ## Selection

package/dist/components/compositions/outcome-panel.d.ts

@@ -28,6 +28,13 @@ export interface OutcomePanelProps {
     class?: string;
     className?: string;
 }
+/**
+ * Re-entry is offered only where the participation ended without the distribution rejecting the
+ * consumer: a lapsed admission (`expired`) or a voluntary exit (`left`). A denial — bot detection,
+ * a validation limit, a draw the consumer simply lost — can leave the distribution open too, so the
+ * eligible reasons are named here rather than inferred from the distribution still accepting entries.
+ */
+export declare function outcomeOffersReentry(outcomeReason: OutcomeReason): boolean;
 export declare function OutcomePanel(props: OutcomePanelProps): import("solid-js").JSX.Element;
 export declare namespace OutcomePanel {
     var displayName: string;

package/dist/components/widgets/experience-widget.d.ts

@@ -172,6 +172,11 @@ export interface ExperienceRenderProps {
 export interface ExperienceWidgetProps {
     experienceId: string;
     autoStart?: boolean;
+    /**
+     * Whether the SDK may enter the consumer on arrival at a distribution the merchant set to enter
+     * automatically. Omit to keep the default (`true`); pass `false` to keep every entry explicit.
+     */
+    automaticEntry?: boolean;
     accessCode?: string;
     autoEnterWaitlist?: boolean;
     theme?: BrandTheme;

package/dist/hooks/use-experience-journey.d.ts

@@ -4,6 +4,12 @@ import { MaybeAccessor } from '../utils/to-accessor';
 export interface ExperienceJourneyOptions {
     accessCode?: MaybeAccessor<string | undefined>;
     autoEnterWaitlist?: MaybeAccessor<boolean | undefined>;
+    /**
+     * Whether core may enter the consumer on the consumer's behalf when routing lands on a
+     * distribution the merchant set to enter on arrival. Left unset, core's default (`true`)
+     * applies; `false` keeps every entry an explicit one the consumer presses.
+     */
+    automaticEntry?: MaybeAccessor<boolean | undefined>;
 }
 export interface UseExperienceJourneyOptions extends ExperienceJourneyOptions {
     autoStart?: MaybeAccessor<boolean | undefined>;