π Feature Description
Background
A common use case of data node selector is to let the user choose some specific data nodes (e.g. results_df) from a list of all scenarios. Many data node configs are auxiliary and irrelevant to the end user.
Currently, the developer needs to use the data_node_selector.datanodes property, and generate the list of data nodes that match the config id of interest.
The filter functionality allows the user to specify this config id, but the develop has no control of specifying it ahead of time.
π‘ Proposed Solution
Possible ideas
- New property for the user to specify config ids
- Allow prepopulating the filter
π Additional Context (Optional)
Related question
When using data_node_selector.datanodes, is it possible to retain the foldable hierarchical scenario -> data node structure in the data_node_selector?
Currently, if I specify a list[DataNode], I only see the data nodes:
π Code of Conduct
β
Acceptance Criteria
π Feature Description
Background
A common use case of data node selector is to let the user choose some specific data nodes (e.g.
results_df) from a list of all scenarios. Many data node configs are auxiliary and irrelevant to the end user.Currently, the developer needs to use the data_node_selector.datanodes property, and generate the list of data nodes that match the config id of interest.
The filter functionality allows the user to specify this config id, but the develop has no control of specifying it ahead of time.
π‘ Proposed Solution
Possible ideas
π Additional Context (Optional)
Related question
When using
data_node_selector.datanodes, is it possible to retain the foldable hierarchical scenario -> data node structure in the data_node_selector?Currently, if I specify a
list[DataNode], I only see the data nodes:π Code of Conduct
β Acceptance Criteria