Add generated samples of each template

[joshka]

No description provided.

[orhun]

LGTM, but how are we planning to keep these up-to-date? One thing that I can think of is that checking the diff in the CI and failing if the generated ones are not updated. Or, even better, we can add a pre-commit hook.

What do you think?

[joshka]

LGTM, but how are we planning to keep these up-to-date? One thing that I can think of is that checking the diff in the CI and failing if the generated ones are not updated. Or, even better, we can add a pre-commit hook.

I'm fine with manually handling this until it's really a pain. I'd much prefer not to have pre-commit hooks doing this update (even though it's actually fairly fast), as these make destructive changes to your workspace.

In general, making changes to a template should look like:

1. change the template
2. re-generate the template using just generate-...
3. check changes in generated files look ok, add to git, but don't commit yet
4. run clippy and fmt to check if these make any changes (if so go back to 1...)
5. commit and PR

Ideally the generated files should not have clippy / formatting problems, because this just pushes these problems out to every end-user that uses these, so fixing them once is a good use of our time.

[joshka]

I added a workspace file to make it easier to run cargo check / clippy / fmt at the repo root

[joshka]

I need to fix the failing check on this at some point

[orhun]

CI logs go crazy for some reason, I guess it's an issue with cargo generate's prompt..

[joshka]

CI logs go crazy for some reason, I guess it's an issue with cargo generate's prompt..

It's due to the custom code that checks for params, but I removed some of them.

[orhun]

Thanks for the pointer @joshka, should be fixed in 73225ec