Enums support

[Egorand]

I was hoping enums are supported, as they're a better alternative to ints for enumerations.

[cmelchior]

Hi @Egorand Enums are on our wishlist as well, but there are some challenges involved as one of the primary design goals of Realm is cross-platform compatibility and enums doesn't exist in Objective-C like they do in Java.

[Egorand]

Hi @cmelchior and thanks for the response, Enums can easily be converted into simple ints and back, I think typedefs are the closest feature that Objective-C provides (my knowledge of Objective-C is close to zero). Hence it shouldn't be hard to represent enums internally in a way that both platforms could work with it.

[cmelchior]

True, but that would be very brittle with regard to modifying the enums afterwards. See here for a discussion on the topic: http://stackoverflow.com/questions/229856/ways-to-save-enums-in-database.

It is possible to find a solution, but right now we want to prioritise other features.

[mpost]

I would also like to see enum support.

[hamen]

+1

[frazer-rbsn]

+1!

[rgrinberg]

+1

[saket]

+1

[AKlimashevskyCedon]

is it possible to help you to speed up enum support?

[StErMi]

Any updates?

[cmelchior]

Right now we are focusing on other bigger features (custom methods, null, async queries and migration API). However once we open up for custom methods it will be possible to work around this by doing the conversion yourself in the getter/setter.

That said we still want to add support for it, but proper support will take a bit longer.

[benjamincombes]

+1

[benjamincombes]

I don't know if it can help anybody, but here is what I use as a workaround :

public enum CampaignStatus {
    LIVE,
    UPCOMING
}

@SerializedName("status")
private String statusRaw;
@Ignore
private transient CampaignStatus status;

public CampaignStatus getStatus() {
    return CampaignStatus.valueOf(getStatusRaw().toUpperCase());
}

public void setStatus(CampaignStatus status) {
    setStatusRaw(status.name());
}

[mateusgrb]

+1

[paulpv]

+1

[musesum]

+1

[doncorsean]

+1

[mehrad-rafigh]

+1

[ddszczygiel]

+1

[Queatz]

+1

[cmelchior]

Note that with #2196 now merged to master (will be part of 0.88), it is possible to support Enums using the following pattern:

public enum MyEnum {
  FOO, BAR;
}

public class Foo extends RealmObject {
  private String enumDescription;

  public void saveEnum(MyEnum val) {
    this.enumDescription = val.toString();
  }

  public MyEnum getEnum() {
    return (enumDescription != null) ? MyEnum.valueOf(enumDescription) : null;
  }
}

[ghost]

+1

[njovy]

+1

[PaulWoitaschek]

@cmelchior Use #Enum.name() instead of toString() as its final.

[oscarg798]

+1

[mateusgrb]

Guys, you can now react to issues/comments with a thumbs up. No more need to comment "+1" =)

[n-belokopytov]

+1

[cmelchior]

@ashk3156 Please create another issue than reusing this one, and please add the code that actually throw the NullPointer as well.

[romshiri]

+1

[nicomlas]

+1