Adding input (preferably optional) to power lora loader. #435
Unanswered
Symbiomatrix
asked this question in
Q&A
Replies: 0 comments
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
Hello @rgthree . I'm currently writing a small modification to the power lora loader based on this node to filter blocks by type and index. Unfortunately, I'm having trouble adding input to the node.
First, I don't know how to add more optional widgets beside FlexibleOptionalInputType(any_type); if I use a dictionary per the standard methods then it'll add an undesirable widget for the lora kwargs. When I add say a block_preset name list (as required), it looks fine at first, but then when the workflow is reloaded the widget goes missing. I think it's because power_lora_loader.js has a custom deserialisation function (configure?), since the text does appear in the json, but I am insufficiently versed with js to understand why.
If I try to add a plain input
("STRING",),anywhere, the node breaks completely.Spare some advice?
Edit: Figured out the breaking was due to it requiring a settings dict (with forceInput to make it a separate node connection), so it at least works basically, but optional dict still breaks loras (none sent to kwargs).
Beta Was this translation helpful? Give feedback.
All reactions