fix(server): support direct variable names in overrideConfig for Agentflow - #6669
Open
iruzen-dono wants to merge 1 commit into
Open
fix(server): support direct variable names in overrideConfig for Agentflow#6669iruzen-dono wants to merge 1 commit into
iruzen-dono wants to merge 1 commit into
Conversation
…tflow
When users pass custom variable values directly in overrideConfig
(e.g. { clasificador: "new_value" }) instead of nested under
overrideConfig.vars, the values were silently ignored because
replaceInputsWithConfig only applied overrides to enabled node input
parameters.
This fix pre-processes overrideConfig to detect keys that match
enabled variable overrides and moves them to overrideConfig.vars,
where getGlobalVariable can resolve them properly.
Fixes FlowiseAI#6651
Contributor
|
Caution The consumer version of Gemini Code Assist on GitHub has been sunset. All code review activity has officially ceased. |
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
When users pass custom variable values directly in
overrideConfig(e.g.{ clasificador: "new_value" }) instead of nested underoverrideConfig.vars, the values are silently ignored byreplaceInputsWithConfigbecause it only applies overrides to enabled node input parameters.This was a regression from v3.0.11 where this format used to work.
Changes
In
replaceInputsWithConfig()inpackages/server/src/utils/index.ts:overrideConfigmatching enabled variable overridesoverrideConfig.varswheregetGlobalVariablecan resolve them properlyoverrideConfig.varsformatRelated Issue
Closes #6651