Skip to content
This repository has been archived by the owner on Jun 11, 2024. It is now read-only.

Improve the UX/DX for creating a module for framework #2863

Closed
nazarhussain opened this issue Feb 11, 2019 · 0 comments · Fixed by #2865
Closed

Improve the UX/DX for creating a module for framework #2863

nazarhussain opened this issue Feb 11, 2019 · 0 comments · Fixed by #2865
Assignees

Comments

@nazarhussain
Copy link
Contributor

Expected behavior

With the json based module specification, it's easy to export, but its difficult to introduce some common behavior to all modules.

Also its not aligned with other framework structs we are providing e.g. To create a new transaction we will specify something like

class MyTransaction extends BaseTransaction {}

We want to align module framework struct with similar way and introduce a BaseModule class.

Actual behavior

Currently we are expecting any module to export a json object in following structure.

{
   alias: '',
   defaults: {},
   load: async () {},
   unload: async () {},
}

Steps to reproduce

Which version(s) does this affect? (Environment, OS, etc...)

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants