30183496
Descripción
Test por Pascal Bartl, actualizado hace más de 1 año
|
Creado por Pascal Bartl
hace más de 3 años
|
|
Pregunta 1
Pregunta
What are AbstractPlugin-based extensions and what is the AbstractPlugin class? (2)
Respuesta
-
Extensions that build an abstraction layer are called AbstractPlugin-based extensions
-
Legacy frontend plugins (also known as pi-based extensions) are usually extension classes of the AbstractPlugin class
-
The AbstractPlugin class contains supporting functions for legacy frontend plugins
-
AbstractPlugin-based extensions must follow a strict convention for names and locations of class files
Pregunta 2
Pregunta
The AbstractPlugin class provided by the core supports legacy extensions in which functions? (1)
Respuesta
-
Database abstraction, template abstraction and frontend/backend separation
-
Extension upgrades, data migration and parsing TCA files
-
Extension installation, extension upgrades, extension activation/deactivation
-
Database access, handling links, pagination, localization (and more).
-
Form creation, mail functionality, object validation by using annotations
Pregunta 3
Pregunta
Which folder names are correct for extensions that use the AbstractPlugin class (not Extbase)? (1)
Respuesta
-
Domain model files must be located in Classes/Domain/Model/
-
Repository files must be located in Classes/Domain/Repository/
-
Class files implementing business logic must be located in Classes/Entity/
-
AbstractPlugin-based extension do not have a convention for the location of class files
¿Quieres crear tus propios Tests gratis con GoConqr? Más información.