07/16/2018, 3:51 PM
If we have a parcelable data class, and the parcelable properties and the other properties you want to be included in equals()/hashcode() aren’t the same, you must implement one of the two yourself! As they both depend on the primary constructor. Why couldn’t the parcelize compiler extension have some annotation to include a property that is not in the primary constructor in the parcelable implementation? Anybody have an idea?