fix: node migration TypeError #4260
Merged
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
webfiltered
requested changes
Jun 24, 2025
|
@webfiltered Thank you for pointing out. I'll make the changes accordingly. |
viva-jinyi
force-pushed
the
fix/custom-node-return-type
branch
from
62c42d4 to
8b110ce
Compare
webfiltered
approved these changes
Jun 25, 2025
|
Awesome - thank you! |
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.
Context
Slack Threads
Added a guard clause for cases where a custom node defines RETURN_TYPES = ("BOOLEAN") instead of a proper tuple like ("BOOLEAN",).
Without the trailing comma, it’s interpreted as a string rather than an array, which causes issues on the frontend.
This fix ensures the frontend can handle such cases more gracefully.
┆Issue is synchronized with this Notion page by Unito