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.
Regards
You can create multiple actions, this should probably be the approach you take.
Chaining actions in the way you suggest doesn’t make a lot of sense with how we have them set up. If an action wasn’t successful, you would probably be denying the user access, meaning you should break from authentication.
Will multiple actions work for you?
Hi Dan, thanks for the answer.
I create two post login actions and it seems they gets executed in order (if so) yes, this is exactly what I was looking for.
Thanks!
Glad that worked for you!
This topic was automatically closed 15 days after the last reply. New replies are no longer allowed.