From 26f6b9354a06d2c371b41d45f68903a5218393ae Mon Sep 17 00:00:00 2001 From: Steve Gordon Date: Wed, 21 Apr 2021 10:58:11 +0100 Subject: [PATCH] Fix incorrect reference in documentation --- .../serialization/custom-serialization.asciidoc | 8 ++++---- .../HighLevel/Serialization/CustomSerialization.doc.cs | 2 +- 2 files changed, 5 insertions(+), 5 deletions(-) diff --git a/docs/client-concepts/high-level/serialization/custom-serialization.asciidoc b/docs/client-concepts/high-level/serialization/custom-serialization.asciidoc index ea682f83496..b562ba8b07a 100644 --- a/docs/client-concepts/high-level/serialization/custom-serialization.asciidoc +++ b/docs/client-concepts/high-level/serialization/custom-serialization.asciidoc @@ -81,7 +81,7 @@ Hooking up the serializer is performed in the `ConnectionSettings` constructor var pool = new SingleNodeConnectionPool(new Uri("http://localhost:9200")); var connectionSettings = new ConnectionSettings( pool, - sourceSerializer: (builtin, settings) => new VanillaSerializer()); <1> + sourceSerializer: (builtin, settings) => new VanillaSerializer()); <1> var client = new ElasticClient(connectionSettings); ---- <1> what the Func? @@ -171,7 +171,7 @@ public class MyFirstCustomJsonNetSerializer : ConnectionSettingsAwareSerializerB } ---- -Using `MyCustomJsonNetSerializer`, we can serialize using +Using `MyFirstCustomJsonNetSerializer`, we can serialize using * a Json.NET `NamingStrategy` that snake cases property names @@ -211,7 +211,7 @@ Hooking up the serializer and using it is as follows var pool = new SingleNodeConnectionPool(new Uri("http://localhost:9200")); var connectionSettings = new ConnectionSettings( pool, - connection: new InMemoryConnection(), <1> + connection: new InMemoryConnection(), <1> sourceSerializer: (builtin, settings) => new MyFirstCustomJsonNetSerializer(builtin, settings)) .DefaultIndex("my-index"); @@ -289,7 +289,7 @@ public class MySecondCustomJsonNetSerializer : ConnectionSettingsAwareSerializer }; protected override ConnectionSettingsAwareContractResolver CreateContractResolver() => - new MySecondCustomContractResolver(ConnectionSettings); <1> + new MySecondCustomContractResolver(ConnectionSettings); <1> } ---- <1> override the contract resolver diff --git a/src/Tests/Tests/ClientConcepts/HighLevel/Serialization/CustomSerialization.doc.cs b/src/Tests/Tests/ClientConcepts/HighLevel/Serialization/CustomSerialization.doc.cs index bf0c842a639..be75e7d19fd 100644 --- a/src/Tests/Tests/ClientConcepts/HighLevel/Serialization/CustomSerialization.doc.cs +++ b/src/Tests/Tests/ClientConcepts/HighLevel/Serialization/CustomSerialization.doc.cs @@ -176,7 +176,7 @@ protected override void ModifyContractResolver(ConnectionSettingsAwareContractRe } /** - * Using `MyCustomJsonNetSerializer`, we can serialize using + * Using `MyFirstCustomJsonNetSerializer`, we can serialize using * * - a Json.NET `NamingStrategy` that snake cases property names * - `JsonSerializerSettings` that includes `null` properties