-
Notifications
You must be signed in to change notification settings - Fork 2.6k
fix: When there are user input parameters in the workflow, the data source setting information is cleared after returning to the previous step from the user input page #4442
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
Merged
Merged
Changes from all commits
Commits
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
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
Oops, something went wrong.
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.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
In your code, there are two potential issues that need to be addressed:
Variable Name Consistency: The variable
keyis used with a capital letter (@Keyin the template) but it should be consistently used as lower case (keyin:key="key"). This consistency can help avoid syntax errors and improve legibility.Component Case Sensitivity: The component names
'DataSource','KnowledgeBase', and their references inak[active]have inconsistent casing which might cause runtime issues depending on your environment’s case sensitivity settings.To optimize the code:
Here's the corrected version of your code snippet:
Make sure to adjust this example to fit within your project structure and integrate the rest of your logic accordingly.