Skip to content

Fix Adapter reactive state lifecycle on Workflow recreation - #82

Merged
dhilt merged 2 commits into
mainfrom
issue-79--adapter-reactive-state-remains-stale-after-recreating-a-Workflow-with-a-partially-customized-datasource
Oct 11, 2026
Merged

dhilt merged 2 commits into
mainfrom
issue-79--adapter-reactive-state-remains-stale-after-recreating-a-Workflow-with-a-partially-customized-datasource

Conversation

@dhilt

@dhilt dhilt commented Oct 11, 2026

Copy link
Copy Markdown
Owner
  • Reset all Adapter reactive properties on disposal, including those omitted from custom configuration.
  • Keep scalar and reactive values consistent when reusing a datasource.
  • Preserve reactive sources and subscriptions across recreation.
  • Extend regression coverage for BOF consistency, initialization notifications and custom-source emissions.

Fixes #79

@dhilt
dhilt merged commit 4fa6066 into main Oct 11, 2026
1 check passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Adapter reactive state remains stale after recreating a Workflow with a partially customized datasource

1 participant