More accurate displaying of enum values.#20
Open
elorest wants to merge 2 commits intoelectronick:masterfrom
Open
More accurate displaying of enum values.#20elorest wants to merge 2 commits intoelectronick:masterfrom
elorest wants to merge 2 commits intoelectronick:masterfrom
Conversation
Now what is actually in the database will be displayed but humanized.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
I've been using your gem for a couple years and really appreciate it. However I occasionally run into issues where I have enum values in the database that don't show up right such as 5'5". Now what is actually in the database will be displayed but still humanized. I also removed the blank value because I want to be able to label the blank value if there is one with the :prompt => "choose height" command.