Update Step 3 on README.md #1065
Open
Conversation
This file contains hidden or 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
the dfx.json proposes a list of cannisters, so if you don't specify which canister you refeer you won't be able to pass the argument as you'll get the following error: Error: The init argument can only be set when deploying a single canister.
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.
the dfx.json proposes a list of cannisters, so if you don't specify which canister you refeer you won't be able to pass the argument as you'll get the following error: Error: The init argument can only be set when deploying a single canister.
Overview
Why do we need this feature? What are we trying to accomplish?
Just correcting documentation so that beginners doesn't have to fix the error.
Requirements
What requirements are necessary to consider this problem solved?
it's a simple solve
Considered Solutions
What solutions were considered?
this solves it
Recommended Solution
What solution are you recommending? Why?
just a little change on documentaiton won't break anything
Considerations
What impact will this change have on security, performance, users (e.g. breaking changes) or the team (e.g. maintenance costs)?
none