additional metadata for attributes

[abx78]

support for additional metadata in the Enum keys

[abx78]

it should fix issue #6

[kindlychung]

Please document your changes in the docstring and create some tests in test/runtests.jl. Thanks.

[abx78]

Sure, I will work on it.

[kindlychung]

I am not convinced that mixing the attributes with the string representation is a good idea. Would be nice if we have two separate operators:

• => for giving a custom string representation, without attributes. This is the previous behavior.
• -> for giving attributes, without a custom string representation. For example, if you define @se Team Barcelona->(country="Spain", revenue=840.8) RealMadrid->(id=3,country="Spain", revenue=757.3), string(Team.Barcelona) would be simply "Barcelona"
• What if the user wants to have both attributes and custom string representation? We can allow a special attribute called repr, whenever the users gives that attribute, we use it as the string representation. For example, if you define @se Team Barcelona->(country="Spain", revenue=840.8, repr="BCLN") RealMadrid->(id=3,country="Spain", revenue=757.3), string(Team.Barcelona) would be "BCLN"

This will be a cleaner design IMHO.