Reorganise server actions: tips?

As the project grows, the server action list is becoming quite a mess.

I want to restructure my folder structure.
For example I want to create a new ‘content’ folder and move the folders ‘audio_content’ and ‘courses’ into it.

However I’m aware that this will cause issues, AFAIK it can break:

  1. Server action calls on the client side (in a form, or a ‘server connect’ element)
  2. Data bindings on the client side
  3. For library actions: break includes and ‘execs’ in other server actions

I am now moving things while doing a search to see if there’s any file referencing this server action. But I feel like I might miss something and wake up to a broken application after finishing reorganising.

This is what I’m doing now:
image

There must be people who’ve done the same. Any tips?

Hi there @karh

I’ve moved main SAs, I’ve not moved library ones.

Just a quick update of the path to your SA in the Server Connect line of your HTML and you are ready to go!

1 Like

Oh, and if I want to make a section of a SA into a Library Action, I just:

  1. Copy the SA
  2. In the copy, remove all steps except the ones that will be in the LA.
  3. Remove all get/post parameters
  4. Rename it and move it to the library folder.
  5. Open in Wappler.

Bingo! You have a Library Action!

1 Like

Thanks @Antony I’ll just procrastinate this for a little while longer but will try it soon :wink:

Btw moving the library server actions didn’t seem much harder than using the replace command I show in the OP