@flytedan/flytebot-design-system 0.12.7 → 0.12.8

package/dist/index.d.cts

@@ -2416,8 +2416,16 @@ interface FeatureGateProps {
     variant?: "block" | "inline";
     /** When false, an incomplete-in-live-mode feature renders `fallback` instead of the ComingSoon banner. Default true. */
     preview?: boolean;
-    /** Permission that lets the viewer bypass the ComingSoon veil and use the feature early. Default "flags.manage". */
-    bypassPerm?: string;
+    /**
+     * Permission that lets the viewer bypass the ComingSoon veil and use the feature early.
+     * Default `"flags.manage"`. Pass `null` to declare the gate NOT bypassable by anyone,
+     * regardless of permissions — the veil still renders, but no "View and use it anyway"
+     * control appears, and a bypass stored from before this call site turned `null` is
+     * ignored rather than honored. Use this for a gate whose content is itself the problem
+     * (e.g. fixture/demo data standing in for another record), where letting even an
+     * administrator click through would show something untrue, not just something unfinished.
+     */
+    bypassPerm?: string | null;
 }
 /** Feature gate. ALWAYS silent when off — an unreleased feature should leave no trace. */
 declare function FeatureGate({ flag, fallback, children, onRoadmap, blur, minHeight, label, variant, preview, bypassPerm }: FeatureGateProps): React.ReactNode;

package/dist/index.d.ts

@@ -2416,8 +2416,16 @@ interface FeatureGateProps {
     variant?: "block" | "inline";
     /** When false, an incomplete-in-live-mode feature renders `fallback` instead of the ComingSoon banner. Default true. */
     preview?: boolean;
-    /** Permission that lets the viewer bypass the ComingSoon veil and use the feature early. Default "flags.manage". */
-    bypassPerm?: string;
+    /**
+     * Permission that lets the viewer bypass the ComingSoon veil and use the feature early.
+     * Default `"flags.manage"`. Pass `null` to declare the gate NOT bypassable by anyone,
+     * regardless of permissions — the veil still renders, but no "View and use it anyway"
+     * control appears, and a bypass stored from before this call site turned `null` is
+     * ignored rather than honored. Use this for a gate whose content is itself the problem
+     * (e.g. fixture/demo data standing in for another record), where letting even an
+     * administrator click through would show something untrue, not just something unfinished.
+     */
+    bypassPerm?: string | null;
 }
 /** Feature gate. ALWAYS silent when off — an unreleased feature should leave no trace. */
 declare function FeatureGate({ flag, fallback, children, onRoadmap, blur, minHeight, label, variant, preview, bypassPerm }: FeatureGateProps): React.ReactNode;

package/dist/index.js

@@ -7910,6 +7910,7 @@ function FeatureGate({
   if (!preview) return fallback;
   const f = SessionKit.findFlag(flag) || {};
   const missing = rt.missing || [];
+  const canBypass = bypassPerm === null ? false : !bypassPerm || SessionKit.can(bypassPerm);
   return /* @__PURE__ */ jsx62(
     ComingSoon,
     {
@@ -7923,7 +7924,7 @@ function FeatureGate({
       minHeight,
       onRoadmap,
       bypassKey: flag,
-      canBypass: !bypassPerm || SessionKit.can(bypassPerm),
+      canBypass,
       children
     }
   );