Namespacing for commands and frontend scaffolding
fadeev opened this issue · 1 comments
Right now there are beaker new
and beaker wasm new
. There will be more code scaffolding commands, and it's a good practice to keep them in the same namespace.
beaker new project
beaker new contract
beaker new contract-counter
beaker new frontend
(doesn't have to be new
, can be scaffold
, create
, etc.)
Currently, beaker wasm new
creates a contract with a counter logic. This is helpful for new devs (to understand how to write a simple contract), but one might also want an empty contract to not have to delete scaffolded code they no longer need, hence beaker new contract
.
This brings me to the frontend, which contains the counter logic, even if a dev hasn't scaffolded a contract yet. The counter logic on the frontend is incredibly simple and the main bits are barely 50 lines long. The proposal is to:
- by default scaffold a frontend without the counter logic
- add
beaker new frontend
in case a user has deleted the frontend dir or they just want to build a frontend - move the frontend logic counter into a short tutorial
That makes a lot of sense! lower priority for now but will do that after next release.