The json library in Play does this thing where it explodes if the json you’re reading is missing a property. Gson would happily leave the property null, but that’s just not the scala way. In scala, if something is optional, it’s wrapped in an
Option. The problem is I’d like to add a property to my data model and I don’t want it to be optional because it’s not.
In Java land, I probably would have added the property and thought about how to deal with migrating old data later, but not in scala. This battle has to be fought right now. That’s what type safe means and it’s why the
NullPointerException has all but died in pure scala apps, not unlike the carpal tunnel epidemic.
In my case I’ve got some data in Couchbase and when I add a new property to my data model, I won’t be able to read the old data. What I need to do is transform the json before hydrating the object. Fortunately, this is a snap by using the rich transformation features described in JSON Coast-to-Coast.
My approach was to create a subclass of
ReadsWithDefaults[A] that reads json and uses a transformation to merge default values. It looks like this:
1 2 3 4 5 6 7 8 9 10
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15