Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Split network from sub-systems #183

Open
eboadom opened this issue Jan 25, 2024 · 0 comments
Open

Split network from sub-systems #183

eboadom opened this issue Jan 25, 2024 · 0 comments

Comments

@eboadom
Copy link
Contributor

eboadom commented Jan 25, 2024

Currently, with yarn generate you are obliged to choose a pool as target, but some proposals don't really deal with pools, only with an specific network.

One idea would be having 2 separate stages on the cli prompt:

  1. Networks. The user chooses 1-to-n networks target.
  2. Sub-systems. The user chooses if the proposal is targetting an Aave pool, or any other sub-system, leaving an "empty" option for when the proposal is too heterogeneous. In this last scenario, using CommonTestBase on the tests, and everything pretty much generic.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant