Document Timeout property behavior for RestClientOptions and RestRequest #2331
+68
−5
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.
Description
Users were unclear about how RestSharp handles
Timeoutvalues of 0, -1, and other negative values. The documentation was minimal and still referenced the obsoleteMaxTimeoutproperty.Purpose
This pull request is a:
Changes
Source Code (XML Documentation)
Enhanced
RestClientOptions.TimeoutandRestRequest.Timeoutwith detailed remarks explaining:Timeout.InfiniteTimeSpanorTimeSpan.FromMilliseconds(-1)TimeSpan.ZeroArgumentOutOfRangeExceptionUser Documentation
configuration.md updates:
MaxTimeoutreference withTimeoutTImeout→TimeoutTimeout Behavior Reference
nullTimeSpanTimeout.InfiniteTimeSpan/TimeSpan.FromMilliseconds(-1)TimeSpan.ZeroArgumentOutOfRangeExceptionExample
Checklist
Original prompt
💬 We'd love your input! Share your thoughts on Copilot coding agent in our 2 minute survey.