Configuring the List Fields
Keep on Learning!
If you liked what you've learned so far, dive in! Subscribe to get access to this tutorial plus video, code and script downloads.
With a Subscription, click any sentence in the script to jump to that part of the video!
Login SubscribeWe've been tweaking a bunch of stuff on the list view. But... what about this big giant table in the middle!? How can we customize that?
Actually, EasyAdminBundle did a pretty good job with it: it guesses which fields to show, humanizes the column header labels and renders things nicely. Good job Javier!
The EasyAdminBundle Profiler
Before we tweak all of this, see that magic wand in the web debug toolbar? Say "Alohomora" and click to open that in a new tab. This is the EasyAdminBundle profiler... and it's awesome. Here, under "Current entity configuration", we can see all of the config we've been building for this entity, including default values that it's guessing for us. This is a sweet map for knowing what can be changed and how.
Under list, then fields, it shows details about all the columns used for the table. For example, under name, you can see type => string. Actually, dataType is the really important one.
Here's the deal: each field that's rendered in the table has a different data type, like string, float, date, email and a bunch others. EasyAdminBundle guesses a type, and it affects how the data for that field is rendered. We can change the type... and anything else you see here.
Controller Fields
How? Under Genus and list, add fields. Now, list the exact fields that you want to display, like id, name and isPublished:
| // ... lines 1 - 80 | |
| easy_admin: | |
| // ... lines 82 - 89 | |
| entities: | |
| Genus: | |
| // ... lines 92 - 94 | |
| list: | |
| // ... lines 96 - 99 | |
| fields: | |
| - 'id' | |
| - 'name' | |
| - 'isPublished' | |
| // ... lines 104 - 121 |
These 3 fields were already shown before.
Let's also show firstDiscoveredAt... but! I want to tweak it a little. Just like with actions, there is an "expanded" config format. Add { } with property: firstDiscoveredAt.
Now... what configuration can we put here? Because this is a date field, it has a format option. Set it to M Y. And, all fields have a label option. Use "Discovered":
| // ... lines 1 - 80 | |
| easy_admin: | |
| // ... lines 82 - 89 | |
| entities: | |
| Genus: | |
| // ... lines 92 - 94 | |
| list: | |
| // ... lines 96 - 99 | |
| fields: | |
| - 'id' | |
| - 'name' | |
| - 'isPublished' | |
| - { property: 'firstDiscoveredAt', format: 'M Y', label: 'Discovered' } | |
| // ... lines 105 - 121 |
Keep going! Add funFact and then one more expanded property: property: speciesCount. This is an integer type, which also has a format option. For fun, set it to %b - binary format!
| // ... lines 1 - 80 | |
| easy_admin: | |
| // ... lines 82 - 89 | |
| entities: | |
| Genus: | |
| // ... lines 92 - 94 | |
| list: | |
| // ... lines 96 - 99 | |
| fields: | |
| - 'id' | |
| - 'name' | |
| - 'isPublished' | |
| - { property: 'firstDiscoveredAt', format: 'M Y', label: 'Discovered' } | |
| - 'funFact' | |
| - { property: 'speciesCount', format: '%b' } | |
| // ... lines 107 - 121 |
Yea know because, scientists are nerds and like puzzles.
Tip
The format option for number fields is passed to the sprintf() function.
If your head is starting to spin with all of these types and options that I'm pulling out of the air, don't worry! Almost all of the options - like label - are shared across all the types. There are very few type-specific options like format.
And more importantly, in a few minutes, we'll look at a list of all of the valid types and their options.
Ok! Close the profiler tab and refresh. Bam! The table has our 6 columns!
Customizing the Search View
Try out the search again: look for "quo". Ok nice! Without any work, the search view re-uses the fields config from list.
You can add a fields key under search, but it means something different. Add fields: [id, name]:
| // ... lines 1 - 80 | |
| easy_admin: | |
| // ... lines 82 - 89 | |
| entities: | |
| Genus: | |
| // ... lines 92 - 106 | |
| search: | |
| // ... line 108 | |
| fields: ['id', 'name'] | |
| // ... lines 110 - 122 |
Out-of-the-box, the bundle searches every field for the search string. You can see that in the queries. But now, it only searches id and name.
Next, let's dive into some of the more interesting field types and their config.
Hi guys,
In my user entity I have set class constants relating to the user type, for example:
const TYPE_STAFF = 0;
const TYPE_SUPERVISOR = 1;
const TYPE_MANAGER = 2;
const TYPE_ADMIN = 3;
Is it possible to display something more descriptive in the list rather than just the id field?