[rust] set useAsyncFileStream only for files in the body #21839
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.
In a previous PR ([Rust ]Add async file stream support for reqwest client): the
useAsyncFileStream
andvendorExtensions.useAsyncFileStream
template variables are used in case there's at least one file uploaded in the body, but they are set as long assupportAsync
is set and any parameter is a file (including if the file is in a form). So these variables are set more often than they should, introducing unused dependencies ontokio
.This explains why on
master
, these tests have thetokio
dependency even though they don't use it:This PR sets the
useAsyncFileStream
andvendorExtensions.useAsyncFileStream
template variables only when at least one body parameter is a file.This PR doesn't break the feature introduced by [Rust ]Add async file stream support for reqwest client, as can be seen in the
samples/client/others/rust/reqwest/file-streaming
example.PR checklist
Commit all changed files.
This is important, as CI jobs will verify all generator outputs of your HEAD commit as it would merge with master.
These must match the expectations made by your contribution.
You may regenerate an individual generator by passing the relevant config(s) as an argument to the script, for example
./bin/generate-samples.sh bin/configs/java*
.IMPORTANT: Do NOT purge/delete any folders/files (e.g. tests) when regenerating the samples as manually written tests may be removed.
master
(upcoming7.x.0
minor release - breaking changes with fallbacks),8.0.x
(breaking changes without fallbacks)"fixes #123"
present in the PR description)@frol (2017/07) @farcaller (2017/08) @richardwhiuk (2019/07) @paladinzh (2020/05) @jacob-pro (2022/10) @dsteeley (2025/07)