feat: add string support to Enum.value/1

[yordis]

Signed-off-by: Yordis Prieto yordis.prieto@gmail.com

Add string support to Enum.value/1 function. The reverse mapping infrastructure was already in place, so I think we should be OK to take in.

[whatyouhide]

What's the reasoning here instead of a Enum.value(Atom.to_string(...))?

[yordis]

@whatyouhide I did not understand your question 😭

The motivation here is that we have these atoms coming as a string from the edge and we have to manually map them to atoms, or do things like String.to_existing_atom/1 that I prefer to avoid, just in case.

So I could use MyEnum.value(v) where v is a string instead of an atom or number.

If I am doing something wrong, please let me know.

[whatyouhide]

Ah I see your point. This looks good to me then. Should we update any docs?

[yordis]

Should we update any docs?

@whatyouhide I looked around, currently, I couldn't figure out where to document this, other than in the CHANGELOG so people are aware of it.

Do you have any suggestions?

[whatyouhide]

CHANGELOG is fine yep!

[yordis]

@whatyouhide done, I also added an example of a previous PR as well

[whatyouhide]

Thank you @yordis 🫶