We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
Hi,
I'm working on dynamic data, with not-predicable fields which can or cannot have multiple items on the same field.
It's giving me headache to test if values are in with key or key.pluralize, so I have removed entirely pluralization of my fork on your gem.
Furthermore, on my use case, I'll put my parsed data on Elastic Search, so I need only singular keys.
I was wondering if you could accept a change like that ? For instance, on a 2.X version.
Regards,
The text was updated successfully, but these errors were encountered:
Hi @Coren, I don't know if you are still interested in the gem or if you are still using it. Sorry for the delay anyway!
As long as an option like that would be configurable, I don't see any reason not to include it.
Have a great weekend
Sorry, something went wrong.
No branches or pull requests
Hi,
I'm working on dynamic data, with not-predicable fields which can or cannot have multiple items on the same field.
It's giving me headache to test if values are in with key or key.pluralize, so I have removed entirely pluralization of my fork on your gem.
Furthermore, on my use case, I'll put my parsed data on Elastic Search, so I need only singular keys.
I was wondering if you could accept a change like that ? For instance, on a 2.X version.
Regards,
The text was updated successfully, but these errors were encountered: