Fix/text input node output to expand to model nodes#203
Open
iammojogo-sudo wants to merge 2 commits into
Open
Conversation
iammojogo-sudo
changed the title
This was referenced Jun 23, 2026
iammojogo-sudo
force-pushed
the
fix/text-input-model-nodes
branch
from
4b59454 to
b07b694
Compare
iammojogo-sudo
force-pushed
the
fix/text-input-model-nodes
branch
from
b07b694 to
e89bb23
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
The Text node has been in the node palette for a while and stores text output fine, but model-type extensions (like my HunyuanDiT t2i) never actually received that text — the runner only sent images. If you wired a Text node into a model it would just throw "No input image selected" and never run.
This PR:
Checks the extension's declared input type — if it's "text", skip the image requirement and send a minimal placeholder instead (the extension ignores it anyway).
Passes the text from any connected source into params["prompt"] so the API gets the prompt.
The multi-input handle routing (input-0, input-1, etc.) that was already in place now also captures nodeInputText from connected sources, so this works for both single and multi-input model nodes.