Remove use case guard clause in schema name prompt #2655
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR removes the use case guard clause in the schema name prompt. When the original work to add the schema name prompt was written (#2647), I made the incorrect assumption that we would only want to prompt for a schema name in the Connector use case. My changes were tested with and intended to work with this PR: apollographql/rover-init-starters#51
Because this work was done as part of the 2025 Hackathon project, a different commit to
rover-init-starters
was merged instead: apollographql/rover-init-starters#52 This version assumes that the schema prompt will happen regardless of project type. This PR adapts 2467 to work with the work that was merged inrover-init-starters
Testing
cargo build
to build theserover
changescargo rover
tolocalrover
withalias localrover='cargo run --manifest-path=/Users/alyssahursh/code/rover/Cargo.toml --bin rover --'
localrover init
supergraph.yaml
file was created using the newly provided schema name