As a developer I want to add easily custom repository actions to the ACA App

[shazada]

We use the extension framework quite extensible and it woks great, let me start with that!

What I see is the time needed to extend or add a custom action to the ADF extension is time consuming. My idea it should be quite similar to how easy in repo or share or in the ng-components https://www.alfresco.com/abn/adf/docs/content-services/components/content-action.component/ it should be.

Now in the extension framework I need to add the following to show a custom action in let's say the context-menu:

1. I need to create a json in the extensions folder ( e.g. test-content-context-menu.json)
2. Create a app.actions.ts in src/app/store
3. Create a app.effects.ts in src/app/store
4. Create a service who actually does the call to the repository

See following blog post (not mine) which sums it up pretty good: https://www.seedim.com.au/hooking-an-adf-document-action-into-a-repo-action/

What we want/discuss about is to have the option to easily create an action without these 4 stops. Sure we know that doing this gives you as a developer ultimate refinery to define and effect your custom action.

Or are we doing this incorrectly?