-
Notifications
You must be signed in to change notification settings - Fork 25
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Symbols? #41
Labels
enhancement
New feature or request
Comments
Hi! |
Could you give me a really high level brief description of where I could
find the part of the code that needs to be changed? I've been poking around
the project but haven't yet located the proper entrypoint for this.
If not that's fine -- I'll find it!!
…On Tue, Jan 12, 2021 at 1:02 PM Misha Merkushin ***@***.***> wrote:
Hi!
Sounds good!
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
<#41 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AAOE4LK3T7WC3VLURK3LP2DSZSFBZANCNFSM4V7IPV5Q>
.
|
I think it is here
I have no more guesses :) |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
My expectation when using this gem was that the values would be automatically returned as symbols, however strings are used by default.
If I submit a pull request that adds the option to have enums be automatically returned as symbols, and make this option configurable and off by default, would that be reasonable, or are you against that line of thinking?
The text was updated successfully, but these errors were encountered: