Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Better handling of data flow #44

Open
MertenD opened this issue Sep 30, 2023 · 0 comments
Open

Better handling of data flow #44

MertenD opened this issue Sep 30, 2023 · 0 comments
Assignees
Labels
enhancement New feature or request

Comments

@MertenD
Copy link
Owner

MertenD commented Sep 30, 2023

Description

Currently all the nodes have a list of values as a output. That is not necessary optimal for many nodes. For example when the extractor node is extracting multiple elements for each of the input elements is might be useful to group the extracted elements together.

Currently it looks like:

Input: [1, 2]
Output: [1.1, 1.2, 2.1]

I need something like this, where the context from where it is coming from remains:

Input: [1,2]
Output: [[1.1, 1.2], [2.1]]

Both Outputs have their own unique use cases. There should be a system that supports both. Maybe it could be useful to do the second approach as a default and to offer an option to flatten the output. Either by creating a new node for it or by putting it as a default option in the options of a node.

@MertenD MertenD added the enhancement New feature or request label Sep 30, 2023
@MertenD MertenD self-assigned this Sep 30, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

When branches are created from issues, their pull requests are automatically linked.

1 participant