feat(cli): solve the no studio flag#379
Merged
lgalabru merged 2 commits intosolana-foundation:mainfrom Oct 20, 2025
Merged
Conversation
Collaborator
|
@zsh28 could you run and push your changes? thanks! |
Contributor
Author
on it! |
Contributor
Author
|
@lgalabru done! |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
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.
Problem:
The --no-studio flag only affected which URL was displayed in the TUI, but the HTTP server always served studio static files regardless of the flag.
Solution:
• Modified start_subgraph_and_explorer_server() to accept an enable_studio parameter
• Conditionally add the studio static files service only when !cmd.no_studio
• The HTTP server still runs (for GraphQL endpoints), but studio UI returns 404 when --no-studio is used