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 currently suffix reoccurring events with a number, though what I really wanted to implement for these is meaningful dynamic name generation.
I postponed this because I didn't feel I have a good take and didn't want to complicate new (and much cleaner) hook event configuration format.
Still this is something that should probably happen and challenges are it would need a (potentially complex) callback, as well as access to non-first argument of the hook.
Tentatively I think about moving in direction of configuration objects (either directly created or intermediary generated from flat array configuration) with distinct interfaces, let's say mandatory Boundary for determining start/stop of the event and optional Name for processing hook arguments and generating a dynamic name.
The text was updated successfully, but these errors were encountered:
I currently suffix reoccurring events with a number, though what I really wanted to implement for these is meaningful dynamic name generation.
I postponed this because I didn't feel I have a good take and didn't want to complicate new (and much cleaner) hook event configuration format.
Still this is something that should probably happen and challenges are it would need a (potentially complex) callback, as well as access to non-first argument of the hook.
Tentatively I think about moving in direction of configuration objects (either directly created or intermediary generated from flat array configuration) with distinct interfaces, let's say mandatory
Boundary
for determining start/stop of the event and optionalName
for processing hook arguments and generating a dynamic name.The text was updated successfully, but these errors were encountered: