Normalize address key to comply with DB column length#121
Merged
danielbachhuber merged 3 commits intolcache:masterfrom May 3, 2017
Merged
Normalize address key to comply with DB column length#121danielbachhuber merged 3 commits intolcache:masterfrom
danielbachhuber merged 3 commits intolcache:masterfrom
Conversation
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
2 participants
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.
Fixes #114
Although the unit tests pass, I was unable to reproduce the exact issue described by the OP.
@rdanamcd Perhaps there is a Pro version of Formidable with more features that I'm not seeing in the free version? Would be great if you could confirm this PR, or provide more exact steps I can use to reproduce. Thanks!