-
Notifications
You must be signed in to change notification settings - Fork 256
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[Feature]: Refactor init to bootstrap examples #867
Comments
Plan for point 1 is to use include_str!. |
Draft #869 created. Questions for @oddgrd or another Shuttle dev:
|
Created by running `cargo shuttle init` and selecting the "none" option. Will be used by shuttle-hq/shuttle#867
This is not currently implemented in #888. I'd recommend splitting it out to a separate issue. (Should be easy.) |
@paulotten Do you want to work on the last part? If not, I can take it. |
…#888) * feat: use `cargo generate` instead of hardcoding examples source code * feat: use `cargo-generate` as a library * feat: add `custom/none` example * use project name `.as_ref()` * fix: apparently we need to use `auto_path` instead of `subfolder`. * chore: update `examples` git submodule * manually set the crate name * fix: clippy lints * fix: rocket sub path * move `use` to top of file * remove the Shuttle.toml file, if it exists * feat: create a .gitignore file when copying an example closes #867 --------- Co-authored-by: Iulian Barbu <14218860+iulianbarbu@users.noreply.github.com>
Describe the feature
We currently bootstrap projects for various service integrations with hard-coded boilerplate code. The current implementation also generates the
Cargo.toml
with the latest available versions, which can be a problem: ‣So for this project we should:
cargo-shuttle
cli to be able to init any example, not just hello-world for each integration.Suggestion or Example of how the feature would be used
No response
Duplicate declaration
The text was updated successfully, but these errors were encountered: