You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I have a code with legacy interactor library (library haven't been updated since Dec. 2019) that I want to convert to a light-service actions. But there is an important piece is missing. Interactor allows you to have an aroundhook for a single service object vs LightService has around_each hook on Organizer, but not on a single Action.
I can customize Action inside my app and add around to MyBaseAction like this:
class MyBaseAction
extend ::LightService::Action
include MyHooks
around :set_data_dog_traces
end
But was wondering if you would consider having around hook for a single Action.
The text was updated successfully, but these errors were encountered:
When we added the around_each Organizer function, we believed that Actions should not be called individually, they should be part of an Organizer. In fact, I don't recall ever creating a single-action Organizer, I always started with two actions.
Is your convention different?
You could throw the action in an Organizer and just invoke it that way. Would that work for you?
I have a code with legacy interactor library (library haven't been updated since Dec. 2019) that I want to convert to a light-service actions. But there is an important piece is missing. Interactor allows you to have an
around
hook for a single service object vs LightService hasaround_each
hook on Organizer, but not on a single Action.I can customize Action inside my app and add
around
to MyBaseAction like this:But was wondering if you would consider having
around
hook for a single Action.The text was updated successfully, but these errors were encountered: