From 23dfd3f595a9d9d6e93e2dff9fac1bc3a5541aaa Mon Sep 17 00:00:00 2001 From: Arne Stockmans Date: Wed, 8 May 2013 14:29:22 +0200 Subject: [PATCH] Renamed is_indexable_callback_class back to is_indexable_callback --- README.md | 8 ++++---- 1 file changed, 4 insertions(+), 4 deletions(-) diff --git a/README.md b/README.md index 822cf3f..5fec319 100644 --- a/README.md +++ b/README.md @@ -577,19 +577,19 @@ You can also choose to only listen for some of the events: If you use listeners to update your index, you may need to validate your entities before you index them (e.g. only index "public" entities). Typically, you'll want the listener to be consistent with the provider's query criteria. -This may be achieved by using the `is_indexable_callback_class` config parameter: +This may be achieved by using the `is_indexable_callback` config parameter: persistence: listener: - is_indexable_callback_class: "isPublic" + is_indexable_callback: "isPublic" -If `is_indexable_callback_class` is a string and the entity has a method with the +If `is_indexable_callback` is a string and the entity has a method with the specified name, the listener will only index entities for which the method returns `true`. Additionally, you may provide a service and method name pair: persistence: listener: - is_indexable_callback_class: [ "%custom_service_id%", "isIndexable" ] + is_indexable_callback: [ "%custom_service_id%", "isIndexable" ] In this case, the callback_class will be the `isIndexable()` method on the specified service and the object being considered for indexing will be passed as the only