dapphub/dapptools

convience methods for skipping library deployment

Open

#881 opened on Dec 7, 2021

View on GitHub
 (1 comment) (0 reactions) (0 assignees)Haskell (323 forks)batch import
good first issue

Repository metrics

Stars
 (2,125 stars)
PR merge metrics
 (No merged PRs in 30d)

Description

deploying libraries can take a long time. One can easily skip this stage if we make it possible to save the deployed library state and pass it to dapp test:

  1. Write a new little dapp helper script which is the dapp --library-addresses above
  2. Make dapp build and dapp --make-library-state use this helper script instead
  3. Allow a flag --state to be passed to dapp test (probably along with env var DAPP_TEST_STATE), which would override the default behaviour of the library deployment that happens automatically

Now if you want to cache this annoying 45s process that happens everytime, you would put:

export DAPP_LIBRARIES=$(dapp --library-addresses)
export DAPP_TEST_STATE=$(dapp --make-library-state)

in your makefile

Contributor guide

Research direction
Study the current library deployment process in dapp, locate the build and test entry points, and implement a flag or environment variable to save and load library state.
Tech stack
haskell
Domain
blockchainbackendtoolingbuild system
Issue type
Feature
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
2
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
Half day
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
Active
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
Clear
Prerequisites
GitBasic command lineFamiliarity with dapptools
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
60