Hey. Just to remind: I'm doing JSON refactoring PR. I have another question: Is it expected that current JSON implementation has more strict behavior for numbers than simple

shouldBe

?

1.shouldBe(1.0)  // passes
"1".shouldMatchJson("1.0")  // throws: "expected 1.0 but was 1"

I think it shouldn't throw. Maybe eq should be used. If you agree, I will fix this. I've already decided to split my PR to multiple ones so it will be one more.

I agree. Use eq