Run scripts/transactions from url
Open
Nobody has claimed this yet.
Feature
Feedback
- Dominant language
- Go
- Stars
- 209
- Forks
- 87
- Avg merge
- 1d 17h
- Merged PRs (30d)
- 3
Description
Description
A lot times I find myself using commands like this:
flow scripts execute <(curl -s "https://raw.githubusercontent.com/onflow/flow-core-contracts/stable-cadence/transactions/flowToken/scripts/get_supply.cdc") -n some_network
It would be nice to support something like this:
flow scripts execute "https://raw.githubusercontent.com/onflow/flow-core-contracts/stable-cadence/transactions/flowToken/scripts/get_supply.cdc" -n some_network
Another potential option is that you would list "sources" in the flow.json:
"sources":{
"core-contracts": "https://raw.githubusercontent.com/onflow/flow-core-contracts/stable-cadence/transactions"
}
and then you could use it like this:
flow scripts execute "core-contracts:transactions/flowToken/scripts/get_supply.cdc" -n some_network
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 scripts execute command and review how it locates script inputs, then inspect the flow.json configuration described in the issue. Clarify whether direct URLs, named sources, or both are in scope; done means the agreed remote-script form works with the documented network option and has coverage for the supported input style.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- cli
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100