You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I was looking for a nice tool that will help me start with project. This looks quite good but I would propose to modify idea a little. This could make a steps that generate a full project instead of using just one source. For example:
Add license (choose one or many)
Add CI (this would be a template that will ask some question and create a basic defaults).
Add keepchangelog
Add code-of-conduct
Setup it as CLI / Webassebly or no_std project.
This idea is to make generate very customable. Instead of using one source allow using many of them. Of course there can conflict - but this would be small disadvantage of this solution.
At the end of day people would be creating own templates in seconds by removing or adding new templates.
This can start with:
cargo generate
Past link to source of 1 template:
> https://git..... (here a link to it)
> Question from this templates
> (..)
Past link to source of 2 template or empty to end:
>
(...)
Threre could be a configuration file in ~/.config/cargo-generate/templates where we could store own steps:
cli:
- http://git...
- http://git..
Usage
cargo generate cli
The text was updated successfully, but these errors were encountered:
Based on my experience, best would be a shell script with a basic for-loop in your URL instead of letting the CLI doing this...
Especially for error handling and user interaction.
relates to #291, so that partials can be used to slice and dice a project into several repositories as well.
Since this is a very specific use case I guess we won't implement a generic "pass as many templates" to compile one project out of it.
I was looking for a nice tool that will help me start with project. This looks quite good but I would propose to modify idea a little. This could make a steps that generate a full project instead of using just one source. For example:
This idea is to make generate very customable. Instead of using one source allow using many of them. Of course there can conflict - but this would be small disadvantage of this solution.
At the end of day people would be creating own templates in seconds by removing or adding new templates.
This can start with:
Threre could be a configuration file in
~/.config/cargo-generate/templates
where we could store own steps:Usage
The text was updated successfully, but these errors were encountered: