This is following @daxida's point that this repository is less easily recommendable to users of codingame since they may not be aware of the tooling of the language they are using in codingame.
In addition, we could have a greater spread of users if we do not implicitly expect them to be comfortable with piping and chaining commands.
I propose that we take a "git" approach with two classes of commands
- Plumbing: low level commands that are intended to build larger commands
- Porcelain: higher level commands that bundle behaviors of plumbing commands together
Every command we have so far can be considered a plumbing command, in this issue I wanted to get opinions on adding porcelain commands like:
- Fetching a puzzle, saving the stub to a file, and opening it in the editor in one command
- Another
run-like command that builds and compiles the solution based on the language and warns users when tooling is missing from their system
- A
watch command or option to the above command that watches for file changes without needing to pipe to anything
This is following @daxida's point that this repository is less easily recommendable to users of codingame since they may not be aware of the tooling of the language they are using in codingame.
In addition, we could have a greater spread of users if we do not implicitly expect them to be comfortable with piping and chaining commands.
I propose that we take a "git" approach with two classes of commands
Every command we have so far can be considered a plumbing command, in this issue I wanted to get opinions on adding porcelain commands like:
run-like command that builds and compiles the solution based on the language and warns users when tooling is missing from their systemwatchcommand or option to the above command that watches for file changes without needing to pipe to anything