Inconsistent `JSON::Serializable` behavior when parsing case-sensitive `Enum`s about crystal HOT 3 CLOSED

JSON (de-)serialization of enums is generally based on lower case. That's not ideal for some use cases, but typically it works quite well as it can parse a range of different spelling variants which you might encounter in unknown JSON sources.

The same is true for Enum.parse, actually. And this is all documented in Enum.parse and Enum#to_json.

If you want a different behaviour for a particular enum type, you can override its .parse and #to_json methods.

from crystal.

I think the catch is foo knows that bar1 is Bar while bar2 is BAr and is reflected in the serialized result as such. However when you deserialize the serialized representation again, it assumes both bar and b_ar are Bar due to how Enum.parse works as called our previously.

I guess the tl;dr is don't use case sensitive enums as they can lead to a lot of confusion like this.

from crystal.

Ok, thanks, that's clear.

But why does serialization, deserialization and again serialization leads to such inconcistent result?

from crystal.