Challenge #1 of 1

Q:
In our CRUD controllers, we deal with the `Field` class. But inside our field configurator, suddenly we are passed a `FieldDto`! Which of the following is most true about these two classes?

When you configure a Field, the data is stored on a FieldDto. Both classes have similar methods, but not identical.

Field extends FieldDto, but adds extra methods to make it easier to configure.

When you configure a Field, its data is stored on a FieldDto. And if you, for example, configure a TextField, its data will be stored on a TextFieldDto.

Field and FieldDto contain the same data and the same methods (though each class has a few extra methods).

Rewatch Video

TRACK

Symfony 7 >

COURSE

EasyAdmin! For an Awesomely Powerful Admin Area >

CHAPTER

Field Configurator Logic

Challenge #1 of 1

Q:
In our CRUD controllers, we deal with the `Field` class. But inside our field configurator, suddenly we are passed a `FieldDto`! Which of the following is most true about these two classes?

TRACK

Symfony 7 >

COURSE

EasyAdmin! For an Awesomely Powerful Admin Area >

CHAPTER

Field Configurator Logic

Challenge #1 of 1

Q: In our CRUD controllers, we deal with the Field class. But inside our field configurator, suddenly we are passed a FieldDto! Which of the following is most true about these two classes?

Q:
In our CRUD controllers, we deal with the `Field` class. But inside our field configurator, suddenly we are passed a `FieldDto`! Which of the following is most true about these two classes?