GeoBoundingBoxFilterTests fails due to wrong deserialization

[andersosthus]

The 3 GeoBoundingBoxFilterTests that tests deserialization of array, verticies and latlon fails on my machine. I guess it's due to culture info (my locale uses , as decimal separator by default).

I've tried to force the Deserializer (NestSerializer._Deserialize) to use InvariantCulture, but that did not fix the issue, so I suspect that this could possibly be a JSON.NET issue.

[Mpdreamz]

@andersosthus mind pasting the output (error message from fluentassertations) of the tests ?

[andersosthus]

Sure:

Expected string to be "0.1, 0.2", but "0,1, 0,2" differs near ",1," (index 1).
   at FluentAssertions.Execution.LateBoundTestFramework.Throw(String message) in d:\Workspaces\FluentAssertions\FluentAssertions.Net35\Execution\LateBoundTestFramework.cs: line 22
   at FluentAssertions.Execution.DefaultAssertionStrategy.HandleFailure(String message) in d:\Workspaces\FluentAssertions\FluentAssertions.Net35\Execution\DefaultAssertionStrategy.cs: line 23
   at FluentAssertions.Execution.AssertionScope.FailWith(String failureMessage, Object[] failureArgs) in d:\Workspaces\FluentAssertions\FluentAssertions.Net35\Execution\AssertionScope.cs: line 165
   at FluentAssertions.Primitives.StringEqualityValidator.ValidateAgainstMismatch() in d:\Workspaces\FluentAssertions\FluentAssertions.Net35\Primitives\StringEqualityValidator.cs: line 47
   at FluentAssertions.Primitives.StringValidator.Validate() in d:\Workspaces\FluentAssertions\FluentAssertions.Net35\Primitives\StringValidator.cs: line 42
   at FluentAssertions.Primitives.StringAssertions.Be(String expected, String reason, Object[] reasonArgs) in d:\Workspaces\FluentAssertions\FluentAssertions.Net35\Primitives\StringAssertions.cs: line 38
   at Nest.Tests.Unit.QueryParsers.Filter.GeoBoundingBoxFilterTests.GeoBoundingBox_Array_Deserializes() in GeoBoundingBoxFilterTests.cs: line 32

[Mpdreamz]

@andersosthus can you confirm a485d68 fixes the issue?

[andersosthus]

I'll test it tomorrow :)

[andersosthus]

@Mpdreamz Yes, that seems to have fixed the problem :)