I was thinking about this while considering issue #399
A solution to the boilerplate utils problem (e.g. when auditing) could be to have another GitHub repo in template mode. This template would have an audit package with already populated Utils module or other containing smart constructors for lovelace, ada, and a few peers alice, bob, etc. An empty test tree and so on.
We would then just need to create new GitHub repos from this template when we want to use cooked for an audit.
This would be public for other people to also be able to quickly get things done with no fear of the blank page syndrome.
I was thinking about this while considering issue #399
A solution to the boilerplate utils problem (e.g. when auditing) could be to have another GitHub repo in template mode. This template would have an
auditpackage with already populatedUtilsmodule or other containing smart constructors forlovelace,ada, and a few peersalice,bob, etc. An empty test tree and so on.We would then just need to create new GitHub repos from this template when we want to use cooked for an audit.
This would be public for other people to also be able to quickly get things done with no fear of the blank page syndrome.