Be able to set scope of an activity
Non planifiée
When workflows grow larger, they contain more and more activities, which makes code completion hard to use. For instance, when typing =$, you will get an endless list of activity names.
What makes things worse is that in the completion list, names are cut off after ~20 characters, so it's impossible to distinguish which is which if they start with the same text
And finally, sometimes it's hard to come up with (globally) unique names for activities. This can sometimes be prevented by using subworkflows, but still...
Can we have an option to set the scope of an activity to the container it is in, or some other option to hide the activity form code completion outside of its container? A good example would be the case where I use a container to do a complex calculation of something, and any intermediate results are never used in the rest of the workflow.
I would be okay with having activities global by default, as long as I can choose to make them local in selected circumstances
-
I can see how this is annoying as a workflow grows larger. The biggest limitation to this is the complexity of implementing such a change. With everything being in the global scope just now, it's quite straightforward. Any references to something l;ke $foo are undefined until after the activity has been executed. Then, it always contains the last result of that activity, no matter where you reference it from.
Reducing the scope would require us to store these variables in separate groups which might get tricky.
Mind you, it might not be as bad as I think. I'll mark it planned and see how far we get.
0
Vous devez vous connecter pour laisser un commentaire.
Commentaires
1 commentaire