Check if dependencies are up-to-date using hash or batching
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 209
- Forks
- 87
- Avg merge
- 1d 17h
- Merged PRs (30d)
- 3
Description
Issue To Be Solved
Currently, flow deps install naiively downloads new copies of all contracts. This impacts performance and risks rate limiting
(Optional): Suggest A Solution
We can improve this by doing a batched hash check against current contract code on-chain to see what is up-to-date.
We should also look into whether we can do batched downloads of dependencies. This depends on what the limits are for script results which will need to be investigated.
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
Start at the flow deps install entry point and investigate how dependencies are currently downloaded. Research batched hash checks against on-chain contract code and script-result limits for batched downloads. Done means up-to-date dependencies are not downloaded unnecessarily and the batching approach works within the relevant limits.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- blockchain, cli
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 25/100