Hi guys, sorry if this is a silly question but I can’t find related information.
There is a way to modularize the action’s code ?
Let’s say, chain actions (ie. run action A and, if A is successful, run action B) or split the action’s code in multiple source files ?
The question is because we are using and action to do a lot of things when a user logs in for the first time (as part of a lazy migration scheme) and the action code is getting too big and we like to split it some way.