Allow customization of a single field without having to define all of them?

[gonzalovilaseca]

AFAIK if only one field needs customization all other fields have to be manually defined or they will not render.
Let's say there is a Person entity with name and gender. If it's define it like this:

easy_admin:
    entities:
        Customer:
            class: Customer
            form:
                fields:
                   - { property: 'gender', type_options: { choices: {'Male'=>'m', 'Female'=>'f' } } }

It will only render gender, so name has to be defined even if it's not customized.
This is painful if the entity has 20 fields and only one has to be customized, so I was thinking of adding this to the configuration:

easy_admin:
    entities:
        Customer:
            class: Customer
            form:
                **hide: [list of fields to hide]**
                fields:
                   - { property: 'gender', type_options: { choices: {'Male'=>'m', 'Female'=>'f' } } }

WDYT?

[javiereguiluz]

I'm closing this issue because we're starting a new phase in the history of this bundle (see #2059). We've moved it into a new GitHub organization and we need to start from scratch: no past issues, no pending pull requests, etc.

I understand if you are angry or disappointed by this, but we really need to "reset" everything in order to reignite the development of this bundle.