Fix issues with null Profile.extra_data field.
Review Request #8293 — Created July 18, 2016 and submitted — Latest diff uploaded
Once upon a time, a user's
Profile.extra_data
defaulted toNone
rather than an
empty dictionary. We recently introduced code that assumes that the field is
non-None
, and we will probably continue to add more and more such code in the
future. This change adds some normalization toUser._get_profile
to make sure
that it's notNone
.
Ran unit tests. Before the fix, the new test failed. After, it succeeds.