flow config add deployment should error on adding conflicts
Open
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 209
- Forks
- 87
- Avg merge
- 1d 17h
- Merged PRs (30d)
- 3
Description
Reported by: Brian Doyle (<@brian.doyle>)
Issue Description:
Instead of resulting in an error with flow project deploy when flow.json has deployments for the same contract on the same network with two different accounts, it should error when you attempt to add the deployment to the second account with flow config add deployment
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start at the flow config add deployment command and compare its validation with the behavior of flow project deploy. Done means adding a deployment for the same contract and network under a different account fails immediately with an error, rather than allowing the conflict until deployment.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- blockchain, cli
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100