Infer recursive dependency aliases for other networks
Open
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 209
- Forks
- 87
- Avg merge
- 1d 17h
- Merged PRs (30d)
- 3
Description
If I have a contract A which I installed that depends on contract B and I give an alias for A, it should infer the alias for B as well using the imported address of B.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
The issue names no files, tests, or entry points. Start by tracing contract installation and network alias handling in flow-cli, then determine how imported contract addresses are represented across networks. Done means assigning an alias to contract A also infers the corresponding alias for its recursive dependency B.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- blockchain, go
- Domain
- blockchain, cli
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100