Skip to content

[✨ FEATURE] Allow specifying config ID for data_node_selector #2851

@arcanaxion

Description

@arcanaxion

πŸ” 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

  1. New property for the user to specify config ids
  2. 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?

Image

Currently, if I specify a list[DataNode], I only see the data nodes:

Image

πŸ“œ Code of Conduct

  • I have checked the existing issues to avoid duplicates.
  • I am willing to work on this issue (optional)

βœ… Acceptance Criteria

  • A working demo or example code (if applicable) is provided.
  • Integration tests demonstrate the new functionality.
  • Any new code is covered by unit tests.
  • Code coverage remains at least 90%.
  • Related documentation updates and release notes are created.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions