A report on X was brought to my attention where someone placed a reusable block (synced pattern) within itself causing a 500 error. This is reminiscent of a previously reported and handled problem described here #18704. As a result of that prior issue, a RecursionProvider component was created as well as simple conventions for preventing recursion on the front end. As noted previously, this was originally implemented in #28405, #28456, #31455. It seems there might be something off with the server warning based on the post on X so this is an issue to follow up to ensure things are working correctly. cc @mcsf who helped implement this work previously!
A report on X was brought to my attention where someone placed a reusable block (synced pattern) within itself causing a 500 error. This is reminiscent of a previously reported and handled problem described here #18704. As a result of that prior issue, a RecursionProvider component was created as well as simple conventions for preventing recursion on the front end. As noted previously, this was originally implemented in #28405, #28456, #31455. It seems there might be something off with the server warning based on the post on X so this is an issue to follow up to ensure things are working correctly. cc @mcsf who helped implement this work previously!