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
Should we natively support returning a class attribute value (or multiple) instead of calling a method of the class during the produce phase?
This could be simple achieved at the JSON level by simply not specifying the method key.
Then, we would have:
"produce": {
"output": [
{
"name": "feature_weights",
"attribute": "feature_importances_" # This would be optional, to be used only if the used name does not match the attribute name.
"type": "list"
}
]
}
The text was updated successfully, but these errors were encountered:
This is a discussion issue as a followup #71
Should we natively support returning a class attribute value (or multiple) instead of calling a method of the class during the produce phase?
This could be simple achieved at the JSON level by simply not specifying the
method
key.Then, we would have:
The text was updated successfully, but these errors were encountered: