Skip to content

Avoid pluralization ? #11

@Coren

Description

@Coren

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,

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type
    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions