Tagging interface defining controller as admin controller.
Tagging interface used to protect certain controllers from brute force attacks
Controllers implementing this interface will be double-checked for admin authentication.
Interface for cart implementations of online shop framework
Interface for cart item implementations of online shop framework
Interface for checkout step implementations of online shop framework
Interface for environment implementations of online shop framework
Interface for IndexService Tenant Configurations
Interface for IndexService Tenant Configurations using elastic search as index
Interface for IndexService Tenant Configurations using factfinder as index
Interface for IndexService Tenant Configurations using findologic as index
Interface for IndexService Tenant Configurations with mockup implementations
Interface for IndexService Tenant Configurations using mysql as index
Interface for getter of product index columns which consider sub object ids and tenant configs
Interface for product list which works based on the product index of the online shop framework
Interface for IndexService workers which support batch processing of index data preparation and index updating
Interface for IndexService workers
Interface for checkout payment provider
Interface for prices returned by price modifcators
Interface for price implementations of online shop framework
Interface for PriceInfo implementations of online shop framework
Adds a gift product to the given cart
Interface to identify product discount actions
Normalizes the composer.json config after merging it from an update. This can include removing invalid configs or package names as the merge process is only additive.
Bricks implementing this interface auto-resolve view and edit templates if has*Template properties are set.
Lazily loads a state if no state is set. When a feature toggle state is requested and no value is registered, the feature manager will delegate initialization to its registered initializers to provide a default state. As soon as there is a state for a specific feature, initializers won't be called anymore.
Defines a bundle which has dependencies on other bundles. When adding a DependentBundle to the collection, the collection will call the static method to register additional bundles.
Used in migrations handling something else than DB migrations (e.g. changing class definitions). As a normal doctrine migration does not know about the dry-run switch (SQL is simply not executed), we need to pass the dry-run state to the migration itself.
Doctrine migrations by default output a warning if no SQL queries were run during a migration. This is perfectly OK for only DB-based migrations, but might happen if a migration changes class definitions which handle their SQL updates implicitely. If a migration implements this interface and doesSqlMigrations() returns false, the warning will be omitted.
Context which is passed to every filter/processor
Defines a component which depends on data providers. Currently supported for
Interface for override handlers which can influence the debug toolbar form and override targeting data based on form results.
This defines the interface for a persistent targeting storage (e.g. Session). The targeting storage needs to define by itself if it needs a unique visitor ID to store data and fetch if from the visitor info itself.
Similar to the TokenStorage for user objects, this contains the current visitorInfo valid for the current request.