Skip to content

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

Description

@dhilt

A datasource created with makeDatasource() and a partial custom reactive configuration can be reused after Workflow disposal. On recreation, an unconfigured reactive property may retain its value from the previous scroller while its scalar counterpart resets.

In a unit reproduction, after setting bof to true, disposing the first Scroller and creating another with the same datasource, adapter.bof is false but adapter.bof$.get() is still true.

Adapter.resetContext() resets only properties present in the custom reactive configuration. Unconfigured reactive properties are reused from the existing Adapter context without being reset. Both forms of a property should reflect the new scroller’s state. A regression test should cover disposal and recreation with a partial configuration.

Activity

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions