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

Node naming convention #151

Open
VGPReys opened this issue Apr 24, 2024 · 1 comment
Open

Node naming convention #151

VGPReys opened this issue Apr 24, 2024 · 1 comment

Comments

@VGPReys
Copy link

VGPReys commented Apr 24, 2024

I believe that using the name node may be confusing, while in haddock3 we call them module.

@sverhoeven
Copy link
Member

I understand the confusion.

The workflow builder is also meant to be used as a generic tool. When used a a generic tool then "node" is a common name used for a building block of a workflow.

The string node is not used that much in the UI maybe we can remove them or make it configurable in the catalog as node_label property.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants