Fix text-find-and-replace node to support text-dictionary-new node #560
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.
Description
This PR resolves an issue with the text find and replace by dictionary node where an error occurs when using a dictionary generated by the text-dictionary-new node. The issue was caused by a type mismatch: the find-and-replace node expects Dict[str, List[str]], while the dictionary node generates Dict[str, str].
Workflow
Changes
Updated the replacement logic to check if the dictionary value is a list. If it is not a list, the value is used directly.
Note:
English is not my first language, and I used an AI assistant (Copilot) to help compose this Pull Request. I appreciate any suggestions to improve clarity or expression.