Enum IDs Can't Be Strings

[pvanb]

Looking at the code referenced in this issue, it doesn't seem possible to create an enum where the id is a string.

You can see this in an example:

class Sex < ActiveEnum::Base
  value :id => 'm', :name => 'Male'
  value :id => 'f', :name => 'Female'
end

will result in:

> Sex['m']
 => nil

Lookup by name works as expected:

> Sex['male']
 => "m"

[adzap]

Yes, it is a limitation of the plugin. I use a type check to decide if the argument to in the [] is an id and you want to return a name, or a name and you want the id.

I've been thinking of moving away from the [] accessor and going with Enum.id(name) and Enum.name(id). Only issue name is defined on Module. But I can override and check for an argument and pass to super if there is no argument.

[kuraga]

@pvanb @adzap Yes, and if we set id to a String - it solves #17

[adzap]

the type is used to determine what you want from the [] accessor. We can't accept string ids without breaking the current behaviour.

[kuraga]

@adzap I know, we talked about it. I say for protocol :) Maybe you will think about new version's behavior...

[adzap]

Perhaps we should explore this more. What is the use case for a string ID? Do you actually use this example in code? Is the enum being used to enumerate attributes on the model?

[kuraga]

@adzap I used it for solving issue #17. I'll explain there.