feat(nodes): add managed file inputs#9302
Open
Gohankaiju wants to merge 3 commits into
Open
Conversation
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
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.
Summary
Closes #9300
This PR adds a first pass of managed file inputs for custom nodes.
It introduces a lightweight
FileFieldflow so node authors can accept document/data files through the InvokeAI UI, instead of requiring users to provide server-local paths or embedding file contents in workflow data. This is especially important for hosted deployments, but is also useful for local/self-hosted users because files can be attached directly from the node input UI.What is included:
FileFieldinvocation field supportfile_idreferencescontext.filesThis first pass is intentionally scoped to node inputs. It does not add gallery/boards integration, previews, thumbnails, search, starring, or bulk file management.
Clearing a node input currently removes the node's reference only. Automatic server-side deletion is left out for now because the same
file_idmay still be referenced by saved workflows, copied nodes, or queued executions.Related Issues / Discussions
Refs #9300
QA Instructions
Automated checks run locally:
Startup smoke test:
Confirmed startup reached
Invoke running on http://127.0.0.1:9090.Still validating before marking ready for review:
FileFieldcontext.filesMerge Plan
Draft PR for design and implementation feedback.
No database schema migration is included. No gallery/boards file lifecycle is introduced in this first pass.
Checklist
What's Newcopy (if doing a release after this PR)