fix(verify): add use_literal_content config option
#3009
Closed
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
rkrasiuk
added
T-bug
|
@mattsse hmm, maybe i should add some warning as well |
|
How does exposing this config help? |
|
@gakonst that's the only way i managed to verify the contract with |
|
why are there urls in the standard-input-json in the first place? |
|
after a few more tests, i'm closing this PR. it appears I'm yet to find the root cause |
|
Hey, was looking for the option to export metadata as a single file with Is there any way to set that option in forge setting ? This is a very useful feature to save the compilation input |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Motivation
Etherscan cannot verify contracts compiled with
via-irand containing more than one contract source. closes #2996Solution
expose the
useLiteralContentsetting