Skip to content
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.

Sign up for GitHub

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

Jump to bottom

feat: preserve UI state memory on API override #3957

Merged
merged 2 commits into from
Feb 3, 2025
Merged

feat: preserve UI state memory on API override #3957

merged 2 commits into from
Feb 3, 2025

Conversation

grapestore
Copy link
Contributor

@grapestore grapestore commented Jan 31, 2025 •
edited
Loading

  • When the state memory is overridden by an API call, the existing UI-based settings get lost.
    This commit ensures that any UI-defined state persists even if an API override occurs.
  • The reason for adding this feature is that, in addition to the input values provided by the API, there are agent-specific states required for maintaining context. We believe having this functionality in place would be highly beneficial.

HenryHengZJ
HenryHengZJ approved these changes Feb 3, 2025
View reviewed changes
Copy link
Contributor

@HenryHengZJ HenryHengZJ left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

thank you !

@HenryHengZJ HenryHengZJ merged commit 2a0e712 into FlowiseAI:main Feb 3, 2025
2 checks passed
@grapestore grapestore deleted the feature/preserve-ui-state-memory branch February 4, 2025 00:14
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Reviewers

@HenryHengZJ HenryHengZJ HenryHengZJ approved these changes

Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.
2 participants
@grapestore @HenryHengZJ