Use `call` for method name in the organizer about light-service HOT 5 CLOSED

Not really. I'll just go with Ruby's duck typing: if it has a public call method, you can invoke it.

from light-service.

With the organizer as the outward facing construct here, I dislike the idea of being required to use an organizer by doing a .call. It makes the API less expressive and removes intent that can be communicated with that method name.

That said, I do like .call as a hidden construct like execute is with actions and the executed macro, but I don't have a solution for what that would look like.

from light-service.

Thanks for the feedback @mattr-!

In order to get orchestrators working properly, we must know what the method is called on the organizer. See the documentation for it here. We could also use metaprogramming to find the one and only (assuming you have one) public class method, but that's error prone.

I've gotten into the habit of using longer organizer names now. So, instead of calling PullsDataFromApi.by_id(x), I just call the organizer PullsDataFromApiById.call(x).

from light-service.

Extending the name of the organizer might be useful here. Any worries about people confusing these with other types of callable objects and passing an object that responds to call that isn't an organizer?

from light-service.

Closing this, as #98 has been merged.

from light-service.