-
Notifications
You must be signed in to change notification settings - Fork 25
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Handling "UI-only" nodes #42
Comments
I've updated, and now I'm getting this:
|
here's my complex workflow, which is the reason I'm looking to go to ComfyScript. I'm running into way too many UI limitations, and it's hard to grok what is different between generations (when I turn knobs, adjust parameters, etc.). |
It's indeed a complex workflow... Can you share the workflow in API format too? There are too many missing nodes on my side and I can't export it in API format correctly. The "Save (API Format)" button will be visible after turning on "Enable Dev mode Options" in the settings of the web UI. |
as requested |
Here's another one: |
Instead of throwing this error, is there a way to do the transpilation programmatically? |
Is there only this error? I've already added a mechanism that will use the API format (which has no UI-only nodes) after the web UI format fails.
You can specify the node where the transpilation starts, e.g. |
Oh, maybe I just need to update again. |
The fallback only exists in the web UI SaveImage hook before. In case you are using the metadata viewer, I've also added fallback to it now. |
Some nodes it seems are client-only nodes, like
Reroute (rgthree)
. I'm getting this error, and I'm assuming that is why, as it's only javascript, there's no associated Python code with it. How should I handle that?The text was updated successfully, but these errors were encountered: