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
When writing DynamicMap callbacks you sometimes want to write a general callback which will work with different numbers of key dimensions. Currently the Callable argspec validation completely prevents this because each key dimension needs to be explicitly named in the callback signature. This makes it completely impossible (or at least very painful) to write a library level callback that handles different numbers of dimensions. I'd very strongly argue that using kwargs should lift the restrictions on validation as it already does for stream parameters.
The text was updated successfully, but these errors were encountered:
I am happy to change policy so this style is not disallowed. It makes validation weaker when used so I in turn would strongly recommend not using this style unless necessary. But I do agree we shouldn't disallow it.
When writing DynamicMap callbacks you sometimes want to write a general callback which will work with different numbers of key dimensions. Currently the Callable argspec validation completely prevents this because each key dimension needs to be explicitly named in the callback signature. This makes it completely impossible (or at least very painful) to write a library level callback that handles different numbers of dimensions. I'd very strongly argue that using
kwargs
should lift the restrictions on validation as it already does for stream parameters.The text was updated successfully, but these errors were encountered: