Organize contribution types and mappings
tenshiAMD opened this issue · 3 comments
It is better to organize types and mappings. I can think of two ways for implementing this one.
- Transfer implementation to CLI
- Create a separate repo (so it can be highly reusable and customizable in the future)
I would move the contribution types and mappings into a separate repository, then utilize both in the CLI and the app.
We should also stop using the CLI in the app, and instead extract the code that is shared between them into a library, then use that library in the CLI and the app separately. We discussed this before but I don't know where. Would you be interested in working on that? I'd greatly reduce the complexity and improve maintainability of the project
We should also stop using the CLI in the app, and instead extract the code that is shared between them into a library, then use that library in the CLI and the app separately.
@gr2m I think it is better if we break down or overview the details so we can track and have better insight. I might need some help with the criteria.