Add an ability to hook into the Apex/Lds/CreateComponent Actions process

Define an ability to assign “hook” functions

List of hooks:

• onPrototypeInit - an attribute on the Lax component. The user will be able to assign function that executes only once. It will be nice to use to define global settings.
• onInit - an attribute on the Lax component. It is local hook to assigne a function that executes when an actual Lax component object created. Due to internal Lax architecture, the system has Lax Prototype object and a list of local Lax objects that inherit the functionality from the Prototype object.
• onResolve/onSuccess - a function to “decorate/change” a resolved value (#20) that went from the server. It will has a default implementation (empty function or not, investigating…) and a user can assign his custom function implementation (in onPrototypeInit, onInit hooks or locally before an actual action queueing)
• onReject/onError - the same logic like for onResolve, but this hook provides an ablity to dive into the error handling process (#19)
• onIncomplete - the same logic like for onReject

[ruslan-kurchenko]

@kvizcarra, @sergey-prishchepa thank you guys for these awesome ideas!

@kvizcarra My original idea is to provide as much flexibility for users as possible. I want to provide an ability to assign listeners/handlers on two stages: prototype init and local init. In the case of the prototype - basically, it would be global listeners for all Lax components (invoked for all Lax component actions). Also, users can assign local listeners for every distinct Lax Prototype Child (invoked for certain Lax component actions) (prototype inheritance).

Using onPrototypeInit and onInit attributes as listeners is more native and straightforward, for me personally. The only one question is - is local Aura.Action invocation works as much synchronously as we need to assign listeners before first ApexAction/LdsAction/CreateComponentAction completed.

As you can see, the idea isn’t only an ability to assign listeners on Apex Actions. I want to add hooks for LdsAction (Lightning Data Service), CreateComponentAction and maybe even for other cases.

@sergey-prishchepa The approach with aura:method is very interesting. When I complete testing with Aura.Action, I’ll try this one and let you guys know the result. Also, I’ll try to show you how it looks like for user perspective and I hope we will find the best approach!

Thank you guys again for your contribution!

[kvizcarra]

1. Is this how onPrototypeInit and onInit will be defined?

<c:lax context="{!this}" onPrototypeInit="{!c.onLaxPrototypeInit}" onInit="{!c.onLaxInit}"/>

1. I don’t quite understand how onResolve/onSuccess and the similar ones are defined. Will the onPrototypeInit and onInit functions be called with an object that allows us to define onResolve/onSuccess?

onLaxInit: function(lax) {
    return lax.onResolve((...) => {...});
}