-
Notifications
You must be signed in to change notification settings - Fork 347
Add support for URL completions in buf curl
#4402
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
Open
stefanvanburen
wants to merge
9
commits into
main
Choose a base branch
from
svanburen/buf-curl-completions
base: main
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
+761
−12
Open
Changes from all commits
Commits
Show all changes
9 commits
Select commit
Hold shift + click to select a range
ce4c55c
Add support for URL completions in `buf curl`
stefanvanburen e1274ba
Add CHANGELOG entry
stefanvanburen 679f2ef
Upgrade to latest app-go@main
stefanvanburen 20a16ea
Add descriptions and error handling
stefanvanburen 37e2fd2
Fix trailing newline
stefanvanburen dd83d77
Merge branch 'main' into svanburen/buf-curl-completions
stefanvanburen 6a9bcc0
Pin app upgrades to main
stefanvanburen 6e02082
Merge branch 'main' into svanburen/buf-curl-completions
stefanvanburen c48c0a6
Use existing curl client
stefanvanburen File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
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
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
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
Oops, something went wrong.
Oops, something went wrong.
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.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
So this pattern makes sense to me, and mirrors the way
buf curlworks in general, but I wonder if we can leverage and refactor the existing code paths to support this.Basically, the command does some validation upfront, sets up the URL, and then sets up the client + resolvers for the schema. I wonder if we can refactor a little bit so that we set up the resolvers for the schema after the validation, and then use that for completions for the URL.
That way, we have a single, consistent code path, and also uses the same
container, client, transport, etc.There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
added in c48c0a6 if I'm understanding properly!