fix: correct curl syntax errors in API examples #468
Conversation
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
- Change -h to -H for header flags (lowercase is help, uppercase is headers) - Change -f to -F for form data flags in file upload example - Use double quotes for Bearer token to enable variable expansion - Remove trailing whitespace after line continuation backslashes
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
Summary
Fixes curl syntax errors that would cause API example commands to fail.
Changes
-h→-H(lowercase is help, uppercase is headers)-f→-F(lowercase is fail-silently, uppercase is form data)$AZURE_AI_AUTH_TOKENto enable shell variable expansionImpact
All curl examples in the affected file were broken and would not execute successfully. These fixes ensure users can copy-paste and run the examples as expected.