ADmad
ADmad
A cleaner way would be to create an `EntityContext` instance from the entity and update `CrudViewHelper::columnType()` to use `EntityContext::type()` to get the field type.
Fixed in a9c7a703438fd8c69dc3695c36273c90203bfa28
This is a good to have feature but there's nothing in the works for it :)
@deizel Can't your particular case be handled just by changing display field of `Facilities` table to `short_name` and then specifying `'facility_id' => ['formatter' => 'relation']` in `scaffold.fields` ?
Well then imo yours is pretty specific use case and using a formatter element or callback is the way to go. You can help documenting it by providing a patch...
Have you tried setting the inputType data attribute for the field to "text" for the ones you want to be text? That's what the JS code checks for https://github.com/FriendsOfCake/crud-view/blob/master/webroot/js/local.js#L57
Sorry, I missed understood the issue. You can set the autocomplete config to false and then add `autocomplete` class to required fields to turn them into autocomplete widgets.
Not sure what the original author intended. But I agree the default doesn't make much sense.
Given that the problem is circumvented by setting `autocomplete` to `false`, I am going to keep this unchanged for now. In any case all the options jugging for autocomplete belongs...
Autocomplete is now used by default only for `select`: 21d75e8f232db365536f757cbaa28b0e5371ea38