The templates/ directory was getting a bit out of hand, so we are updating it to only include transactions that we expect to execute more than once. If a new transaction needs to be added to this repo and it is only a one-off transaction, it should be saved in the directory where the transaction's README and arguments go. If it is expected to be run more than once, then it can still go in the templates/ directory.
To align with this, I moved all of the previous one-off transactions into their respective directories. I also moved transactions to specific directories that for whatever reason will never be run again, such as old end epoch transactions (since epochs are automated now).
I also included instructions for this in the README
Updates Transactions to Cadence 1.0
I updated all the existing transactions that we may use again to Cadence 1.0. Almost all of these were just copied directly from the flow-core-contracts repo, so they have been tested there.
Closes #298
This PR does two major things:
Reorganizes Transactions
The
templates/directory was getting a bit out of hand, so we are updating it to only include transactions that we expect to execute more than once. If a new transaction needs to be added to this repo and it is only a one-off transaction, it should be saved in the directory where the transaction's README and arguments go. If it is expected to be run more than once, then it can still go in thetemplates/directory.To align with this, I moved all of the previous one-off transactions into their respective directories. I also moved transactions to specific directories that for whatever reason will never be run again, such as old end epoch transactions (since epochs are automated now).
I also included instructions for this in the README
Updates Transactions to Cadence 1.0
I updated all the existing transactions that we may use again to Cadence 1.0. Almost all of these were just copied directly from the
flow-core-contractsrepo, so they have been tested there.