Feature -- Create Missing Artifacts #2
Merged
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
…here is an entry for it in the networks file
… against the output directory (which will have all of the input dir's updated artifacts if any existed)
|
@chuckbergeron Could you close and reopen this one? Github seems to think there are way more changes |
asselstine
approved these changes
Jan 10, 2019
|
Ah- also maybe add a mention in the readme that input artifacts aren't strictly needed. Perhaps something like 'merge into existing Truffle artifacts or create new ones'. Maybe even a short section? |
…g apply-registry generate the artifacts for you to readme
|
@asselstine Readme updated and Promises converted to async/await ! |
asselstine
approved these changes
Jan 13, 2019
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.
This will generate any artifact files in the output artifacts directory which did not exist in the input artifacts directory.
For instance, if the input directory has a 'Migrations.json' artifact, and a networks file has contract addresses for 'Migrations' and 'SimpleToken', then the output artifact directory will have both artifacts for 'Migrations' and 'SimpleToken'.
This is useful when you manually add contract addresses (possibly which others have deployed to testnets, mainnets, etc) to a networks file and want to consume addresses in the artifacts files.