Resolve app addresses from DAO name in dao.json

[yeqbfgxjiq]

Moved over from aracred/onboarding#5

Right now the person who sets up AraCred needs to manually input daoAddress, tokenManagerAddress and votingAddress.

It'd be way easier if they could just input the ENS name of the DAO (we can label it as daoName).

[yeqbfgxjiq]

@Evalir how easy/hard is this to setup?

[pythonpete32]

The problem with this is it assumes the DAO will have only one token manager or voting app which is not always the case

[Evalir]

Yes; as Aaron says, there are a few UX concerns to this:

• We cannot assume a user will only have one token manager or voting app instance; we can filter out only these instances and let the user choose which one he wants to activate, but this makes the CLI questionnaire quite long. Also, if he has a different "voting" app, such a custom voting app or dot voting, I'm not sure Aracred will work correctly.
• We will need to add @aragon/wrapper for this, and, this package is quite heavy and extensive; this makes the CLI heavier, and so it makes the download time increase. I don't think this is desired, as downloading packages from NPM is already quite slow.

We may be able to implement this smoothly once the toolkit's ready, but there's no good timeframe for these features to be ready other than Q2 2020.

[pythonpete32]

plumbery (toolkit) is going to be released this week, what priority It would be nice to refactor the whole codebase using plumber. we can overcome a lot of the pain setting up Aracred