ethereum-optimism / ethereum-optimism/optimism

op-deployer: deprecate non-forge artifact setup

Open
#18,346 0 comments 0 reactions 0 assignees View on GitHub
A-op-deployer
Dominant language
Go
Stars
6.5k
Forks
4k
Avg merge
2d 15h
Merged PRs (30d)
145

Description

Description
With forge now we're requiring the entire folder to be present (with the solidity source files). We still have code in op-deployer that supports loading non-forge compatible artifacts, which would ultimately fail to work.

Contributor guide

Open the contributing guide

Research direction

Start by locating op-deployer's artifact setup and the code paths for non-forge-compatible artifacts. Confirm the forge requirement and identify tests covering artifact loading; done means non-forge setup is deprecated and affected tests reflect the supported folder-based layout.

Written by the indexing model from the issue text.

Assessment

Tech stack
go, solidity
Domain
tooling
Issue type
Refactor
Difficulty
3/5
Estimated time
1-2 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.