Do we really need to Server Restrict every single Server Action we want to protect?

We did introduce the global action that always run first. So common logic you can put in there.

Similar idea is also to have common action per folder indeed. But should it execute for server actions directly under this folder or any children even nested ones.

Although it does sounds great when we consider it, it does have some disadvantages.

Most important one is that you loose any overview of which actions ran automatically before the current one.

People already have trouble with single global action and forget that they added things in there, lets stay a multi level global actions from all parent folders.

You will be pulling your hair out debugging this.

So that was what stopped us from implementing it yet.

2 Likes