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 processing the results from a collection in a collection notebook, it is sometimes very handy, or even essential, to know how the artifact was called. This is easy enough to do manually, but not if one wants to write a vql_suggestion in the artifact.
I am not sure how these parameters are best made available, either directly in the scope, through a scope object, or by calling a function. For a vql_suggestion, accessing the parameters from the current scope would be nice.
The text was updated successfully, but these errors were encountered:
When processing the results from a collection in a collection notebook, it is sometimes very handy, or even essential, to know how the artifact was called. This is easy enough to do manually, but not if one wants to write a vql_suggestion in the artifact.
I am not sure how these parameters are best made available, either directly in the scope, through a scope object, or by calling a function. For a vql_suggestion, accessing the parameters from the current scope would be nice.
The text was updated successfully, but these errors were encountered: