Support service/method tuples as indexable callbacks. Closures are also supported, although they cannot be injected by the service container.
The indexable callback is now injected via a setter and validated when set (instead of during event processing).
Added optional is_indexable_callback config param to persistence. If this is a method on the entity, the listener will only process it if the method returns true. Also updated documentation.
* Created AbstractProvider class (for all DB services), which handles the default batch_size option.
* The logger Closure is now optional for populate().
* Removed unused Elastica_Type argument from Provider constructors.
* Added unit tests for Doctrine's AbstractProvider class.
* The extra argument (ManagerRegistry) for Doctrine providers is now an appended constructor argument, so the extension no longer needs to use different replacement indexes for Propel/Doctrine providers.
This introduces a registry service for persistence providers.
Previously, tagging one or more provider services would cause AddProviderPass to clobber the default providers created by the bundle's extension class. Now, the extension class tags its created providers and allows them to be registered via RegisterProvidersPass just like custom providers.
BC break: Custom providers tagged "foq_elastica.provider" must now specify a "type" attribute on their tag. An "index" attribute is optional (the default ES index will be used by default).
The driver option is not required by the configuration, so we should check for it the validation functions.
If type_prototype is being used, there is a legitimate case where type definitions would not specify a driver. Likewise, the type_prototype may not specify the driver. If we wish to validate that a driver has been specified for a type, we'll have to do that in the extension class after loading the configuration and merging in prototypes.
The driver option is not required by the configuration, so we should check for it the validation functions.
If type_prototype is being used, there is a legitimate case where type definitions would not specify a driver. Likewise, the type_prototype may not specify the driver. If we wish to validate that a driver has been specified for a type, we'll have to do that in the extension class after loading the configuration and merging in prototypes.
