Could we implement addBehavior()? about elastic-search HOT 7 CLOSED

if we can not use behaviors now, is there any workaround?

from elastic-search.

Behaviors are a bit tricky. While we could add them, I have concerns that many core and userland behaviors don't make sense in elastic search. For example TreeBehavior, TranslateBehavior make no sense and really have no way of properly functioning.

from elastic-search.

@markstory you are right, but in this case there are other plugins like file-upload that need before/after save logic. With no behaviors we must create custom listeners somewhere and add callbacks for Model.before/afterSave

I tried to see how behaviorRegistry works, it accepts a Table object on its constructor, if we will implement behaviors...should we modify it or create another one "registry" ?

Thanks!

from elastic-search.

@markstory for example the FriendsOfCake/Search plugin too.

from elastic-search.

I don't think it is a good idea. At least using "behaviors" as a word is not a good idea. We could perhaps duplicate the concept with a different name.

from elastic-search.

This issue is stale because it has been open for 120 days with no activity. Remove the stale label or comment or this will be closed in 15 days

from elastic-search.

My current use case that seems to call for a behavior is that I have a SQL table and an Elasticsearch index that represent data with the same fields, and I'd like to have them share custom finder methods. I don't think that this can be accomplished well with traits or class inheritance.

from elastic-search.