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
Often, hooks are mainly required to change the behaviour depending on some external data and to get the information from the server about a state. It is often required to reference external information while running hooks.
I am suggesting a Metadata field in Client struct which will be of type map[string]interface{}. Any arbitrary value can be stored in the field which gets passed along to hooks and can be used very easily.
P.S - There is a Key Value slice available in UserProperties but that can not store arbitrary data types
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
Often, hooks are mainly required to change the behaviour depending on some external data and to get the information from the server about a state. It is often required to reference external information while running hooks.
I am suggesting a
Metadata
field inClient
struct which will be of typemap[string]interface{}
. Any arbitrary value can be stored in the field which gets passed along to hooks and can be used very easily.P.S - There is a Key Value slice available in UserProperties but that can not store arbitrary data types
Beta Was this translation helpful? Give feedback.
All reactions