You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
It appears that the RequestConfiguration property of PlainRequest is not being used during the execution of the request.
For example, it is possible to initialize a request (e.g., SearchTemplateRequest) with a custom request configuration using PlainRequest.RequestConfiguration. However, during the actual execution within the client, only Request.RequestConfig is used — which seems to be independent of the previously configured RequestConfiguration.
Example:
When stepping through the execution, it becomes clear that only RequestConfig is referenced, and the configuration provided via the descriptor (e.g., DisablePing) is lost.
This seems like an oversight. There should likely be an initialization or transfer of the RequestConfiguration data to RequestConfig during request setup to preserve the intended behavior.
The text was updated successfully, but these errors were encountered:
It appears that the
RequestConfiguration
property ofPlainRequest
is not being used during the execution of the request.For example, it is possible to initialize a request (e.g.,
SearchTemplateRequest
) with a custom request configuration usingPlainRequest.RequestConfiguration
. However, during the actual execution within the client, onlyRequest.RequestConfig
is used — which seems to be independent of the previously configuredRequestConfiguration
.Example:
When stepping through the execution, it becomes clear that only
RequestConfig
is referenced, and the configuration provided via the descriptor (e.g.,DisablePing
) is lost.This seems like an oversight. There should likely be an initialization or transfer of the
RequestConfiguration
data toRequestConfig
during request setup to preserve the intended behavior.The text was updated successfully, but these errors were encountered: