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
Similar to #33027 but for async requests that require two requests to be issued (one to start the async processing, and one to actually do the dispatch).
I am not sure why we'd need those to be separated for the AssertJ support since it's stateful.
This could be one of those cases where we want to take the current response as an input parameter and produce an Assert object that results from performing another exchange using that input.
The text was updated successfully, but these errors were encountered:
This commit improves the handling of asynchronous requests by offering
a way to opt-in for the raw async result. This provides first class
support for asserting a request that might still be in process as well
as the asyncResult, if necessary.
See gh-33040
Similar to #33027 but for async requests that require two requests to be issued (one to start the async processing, and one to actually do the dispatch).
I am not sure why we'd need those to be separated for the AssertJ support since it's stateful.
This could be one of those cases where we want to take the current response as an input parameter and produce an Assert object that results from performing another exchange using that input.
The text was updated successfully, but these errors were encountered: