`call` interface about light-service HOT 8 CLOSED

I've been using the method name call for my organizers recently. I open to it.

from light-service.

Ok you reply fast. Sorry, I just realized - I meant actions. This is useful when making organizer-actions.

from light-service.

How is it useful? Can you provide examples?

from light-service.

Sometimes, I make an organizer-action that is used in an action, or can be used alone. This will make the code slightly shorter. Also, when testing an action individually, I will be able to invoke call or .() instead.

It could/should be an alias.

from light-service.

I think that would be a small gain for this change. The convention I've been using is Organizer#call and Action#execute - class level methods. Also, how would the executed class level macro look?

from light-service.

@adomokos - the executed macro would be the same. This would be an alias for Action.execute.

from light-service.

You could just open the class and add that alias for you through metaprogramming. I don't see this - yet at least - somehting I'd add to LS.

from light-service.

Yes, I could. Alright - thanks!

from light-service.