You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Jun 11, 2024. It is now read-only.
User can only define actions for a module in the module specification as an object, where keys of object are action names.
Load those actions object in the controller properly (already have some implementation but need refactoring)
The rest of the flow works exactly the same
Actual behavior
In current implementation the flow for actions is as below:
At the time of module initialization, it provide array of actions (string names) that module supports.
Controller pass the channel object while loading the module
Module can actually define the action by using channel.action method during module loading async load method.
This flow does makes some ambiguity and difficult user flow. User may define the actions in different files, but forget to mention those in the module specification and vice versa. And its also difficult to find where the actions for particular modules are listed.
Which version(s) does this affect? (Environment, OS, etc...)
1.6.0
The text was updated successfully, but these errors were encountered:
Expected behavior
Modify the implementation with these guidelines:
channel.action
completelyActual behavior
In current implementation the flow for actions is as below:
channel.action
method during module loadingasync load
method.This flow does makes some ambiguity and difficult user flow. User may define the actions in different files, but forget to mention those in the module specification and vice versa. And its also difficult to find where the actions for particular modules are listed.
Which version(s) does this affect? (Environment, OS, etc...)
1.6.0
The text was updated successfully, but these errors were encountered: