Related changes in the docs

Fixed the failing parameters parsing tests

Author: alexeyzimarev

docs/.vuepress/config.js

@@ -11,7 +11,7 @@ module.exports = {
     themeConfig: {
         logo: "/restsharp.png",
         navbar: [
-            {text: "Migration to v107", link: "/v107/"},
+            {text: "Migration from legacy", link: "/v107/"},
             {text: "Documentation", link: "/intro.html"},
             {text: "Get help", link: "/support/"},
             {text: "NuGet", link: "https://nuget.org/packages/RestSharp"}
@@ -34,7 +34,7 @@ module.exports = {
             "/v107/": [
                 {
                     text: "",
-                    header: "Migration to v107",
+                    header: "Migration from legacy",
                     children: [
                         "/v107/README.md"
                     ]

docs/README.md

@@ -5,7 +5,7 @@ heroText: RestSharp
 tagline: Probably, the most popular REST API client library for .NET
 actions:
 - text: Get Started →
-  link: /v107/
+  link: /intro.html
 features:
 - title: Serialization
   details: JSON, XML and custom serialization and deserialization
@@ -24,7 +24,7 @@ footer: Apache 2.0 Licensed | Copyright (c) .NET Foundation and Contributors
 
 RestSharp is probably the most popular HTTP client library for .NET. Featuring automatic serialization and deserialization, request and response type detection, variety of authentications and other useful features, it is being used by hundreds of thousands of projects.
 
-RestSharp passed over 165 million downloads on NuGet, with average daily download count close to 42,000. It's being used by many popular OSS projects, including Roslyn and Swagger.
+RestSharp passed over 190 million downloads on NuGet, with average daily download count over 43,000. It's being used by many popular OSS projects, including Roslyn and Swagger.
 
 Supported by [AWS](https://aws.amazon.com/developer/language/net/solutions/).
 <div style="text-align: center;"><a href="https://aws.amazon.com"><img src="/aws_logo.png" alt="AWS logo"></a></div>

docs/v107/README.md

@@ -1,10 +1,10 @@
 ---
-title: RestSharp Next (v107)
+title: RestSharp Next (v107+)
 ---
 
-## RestSharp v107
+## RestSharp v107+
 
-The latest version of RestSharp is v107. It's a major upgrade, which contains quite a few breaking changes.
+RestSharp got a major upgrade in v107, which contains quite a few breaking changes.
 
 The most important change is that RestSharp stop using the legacy `HttpWebRequest` class, and uses well-known 'HttpClient' instead.
 This move solves lots of issues, like hanging connections due to improper `HttpClient` instance cache, updated protocols support, and many other problems.
@@ -17,7 +17,7 @@ Finally, most of the interfaces are now gone.
 
 ### RestClient and options
 
-The `IRestClient` interface is deprecated. You will be using the `RestClient` class instance.
+The `IRestClient` interface is deprecated in v107, but brought back in v109. The new interface, however, has a much smaller API compared to previous versions. You will be using the `RestClient` class instance.
 
 Most of the client options are moved to `RestClientOptions`. If you can't find the option you used to set on `IRestClient`, check the options, it's probably there.
 
@@ -187,23 +187,16 @@ The next RestSharp version presumably solves the following issues:
 ## Deprecated interfaces
 
 The following interfaces are removed from RestSharp:
-- `IRestClient`
 - `IRestRequest`
 - `IRestResponse`
 - `IHttp`
 
-### Motivation
-
-All the deprecated interfaces had only one implementation in RestSharp, so those interfaces were abstracting nothing. It is now unclear what was the purpose for adding those interfaces initially.
-
-What about mocking it, you might ask? The answer is: what would you do if you use a plain `HttpClient` instance? It doesn't implement any interface for the same reason - there's nothing to abstract, and there's only one implementation. We don't recommend mocking `RestClient` in your tests when you are testing against APIs that are controlled by you or people in your organisation. Test your clients against the real thing, as REST calls are I/O-bound. Mocking REST calls is like mocking database calls, and lead to a lot of issues in production even if all your tests pass against mocks.
-
-As mentioned in [Recommended usage](#recommended-usage), we advise against using `RestClient` in the application code, and advocate wrapping it inside particular API client classes. Those classes would be under your control, and you are totally free to use interfaces there. If you absolutely must mock, you can mock your interfaces instead.
-
 ### Mocking
 
 Mocking an infrastructure component like RestSharp (or HttpClient) is not the best idea. Even if you check that all the parameters are added correctly to the request, your "unit test" will only give you a false sense of safety that your code actually works. But, you have no guarantee that the remote server will accept your request, or if you can handle the actual response correctly.
 
+However, since v109 you can still mock the `IRestClient` interface, but you only need to implement the `ExecuteAsync` method. The `ExecuteAsync` method is the only one that actually makes a call to the remote server. All other methods are just wrappers around it.
+
 The best way to test HTTP calls is to make some, using the actual service you call. However, you might still want to check if your API client forms requests in a certain way. You might also be sure about what the remote server responds to your calls with, so you can build a set of JSON (or XML) responses, so you can simulate remote calls.
 
 It is perfectly doable without using interfaces. As RestSharp uses `HttpClient` internally, it certainly uses `HttpMessageHandler`. Features like delegating handlers allow you to intercept the request pipeline, inspect the request, and substitute the response. You can do it yourself, or use a library like [MockHttp](https://github.com/richardszalay/mockhttp). They have an example provided in the repository README, so we have changed it for RestClient here:

test/RestSharp.Tests/ObjectParserTests.cs

@@ -31,7 +31,7 @@ public void ShouldProduceMultipleParametersForArray() {
             SomeIds = new[] { 1, 2, 3 }
         };
         var expected = request.SomeIds.Select(x => ("ids[]", x.ToString()));
-        var parsed   = request.GetProperties();
+        var parsed   = request.GetProperties().Select(x => (x.Name, x.Value));
 
         parsed.Should().BeEquivalentTo(expected);
     }