@plasmicapp/react-web 0.2.229 → 0.2.230

package/dist/react-web.esm.js

@@ -218,7 +218,7 @@ function triggerLogin(appId, authorizeEndpoint, redirectUri) {
     });
 }
 function PlasmicPageGuard(props) {
-    var appId = props.appId, authorizeEndpoint = props.authorizeEndpoint, minRole = props.minRole, canTriggerLogin = props.canTriggerLogin, children = props.children;
+    var appId = props.appId, authorizeEndpoint = props.authorizeEndpoint, minRole = props.minRole, canTriggerLogin = props.canTriggerLogin, children = props.children, unauthorizedComp = props.unauthorizedComp;
     var dataSourceCtxValue = usePlasmicDataSourceContext();
     React__default.useEffect(function () {
         if (canTriggerLogin) {
@@ -249,12 +249,24 @@ function PlasmicPageGuard(props) {
         }
         return dataSourceCtxValue.user.roleIds.includes(minRole);
     }
+    /*
+    PlasmicPageGuard has three cases:
+    1. No value of dataSourceCtxValue, user is loading or a trigger login should be performed.
+       In this case, we don't want to render the children or the access denied message.
+       While the user is loading we look to see if don't have a user value as we can be in a
+       revalidate state.
+    2. The user doesn't have access to the page in which we show an access denied message.
+    3. The user has access to the page in which we render the children.
+    */
     if (!dataSourceCtxValue ||
-        dataSourceCtxValue.isUserLoading ||
+        (dataSourceCtxValue.isUserLoading && !dataSourceCtxValue.user) ||
         (!dataSourceCtxValue.user && minRole && canTriggerLogin)) {
         return null;
     }
     if (!canUserViewPage()) {
+        if (unauthorizedComp) {
+            return React__default.createElement(React__default.Fragment, null, unauthorizedComp);
+        }
         return React__default.createElement("div", null, "You don't have access to this page");
     }
     return React__default.createElement(React__default.Fragment, null, children);