Closed Arcitec closed 11 months ago
If you have fixes, or well rewrites probably in a lot of cases please make a PR. Most of this needs a rewrite. I basically had been learning Python with this. Some nodes were just never finished and pushed along with other nodes, too. Found some of those a few months ago.
I don't have the time to work on this project right now (or many others).
Ah I see. I can thank you for inspiring me to learn how to write ComfyUI nodes. Since this was broken, I spent a few hours researching and developing some nodes, and that's mostly thanks to you. ^^
There's a trick that can be done to merge all these incoming texts via **kwargs
. I'll see if I have time to make a rewrite and pull request for this node tomorrow!
Ah I see. I can thank you for inspiring me to learn how to write ComfyUI nodes. Since this was broken, I spent a few hours researching and developing some nodes, and that's mostly thanks to you. ^^
There's a trick that can be done to merge all these incoming texts via
**kwargs
. I'll see if I have time to make a rewrite and pull request for this node tomorrow!
I knew I should have used kwargs from the beginning, cause it's actually not fun adding all the params across a custom node lol
Hi, thanks a lot for this node pack. I'm working my way through the text nodes to try to make a dynamic prompt workflow. So far I'm using a bunch of
Text Multiline
nodes into aText List
node, which allows me to Bypass anyText Multiline
boxes to rapidly toggle certain parts of the prompt.All I need now is to convert that list of
["a", "b", "c"]
strings into a single comma-delimited String for use in prompting.So I noticed that the
Text List
node's output is only compatible with theWAS_Text_List_Concatenate
node. And I see that it has a "delimiter" input. So I assume that it's meant to turn the provided lists into a concatenated string.If so, there are many bugs in the source code of the
WAS_Text_List_Concatenate
node:delimiter
parameter is not used whatsoever. It's literally not used in the code at all.delimiter
is marked as a REQUIRED parameter. But if we provide it, the node bugs withWAS_Text_List_Concatenate.text_concatenate_list() got an unexpected keyword argument 'delimiter
because the node isn't coded properly to take that parameter, hehe.list_b
is marked as a REQUIRED parameter too. If the purpose is to concatenate 1+ lists into a text string, it should only require thelist_a
. The rest should be optional.delimiter
was an internal text field (which can be converted to an input if needed), so we don't need to connect a separateText
node just to provide a delimiter.PS: Adding a new, separate node that is able to concatenate lists would also be a good idea to complete the suite, basically to allow merging many separate
Text List
into one big list before concatenating it all into a text string with a final delimiter.