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.

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

Hotfix: Publish event emitters keep a reference to the previous subscribers when cloned in a repeatable container #2300

Merged
merged 1 commit into from
Jul 30, 2024

Conversation

andrewbrazzatti
Copy link
Contributor

To add a new element, repeatable containers clone the first element to add a new one. The publish event emitters after cloning still hold their previous subscribers which means the sub-elements in the first elements subscribing react to changes in the new element. This fix creates new event emitter objects for each publish event so that it no longer occurs.

…lone as the existing subscribers are not cleared by the clone.
Copy link

codecov bot commented Jul 30, 2024

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 70.09%. Comparing base (7dc5b7c) to head (77e9d43).

Additional details and impacted files
@@           Coverage Diff           @@
##           master    #2300   +/-   ##
=======================================
  Coverage   70.09%   70.09%           
=======================================
  Files         112      112           
  Lines        1876     1876           
  Branches      218      218           
=======================================
  Hits         1315     1315           
  Misses        561      561           
Flag Coverage Δ
frontend-core-lib 52.41% <ø> (ø)
frontend-dashboard 88.07% <ø> (ø)
frontend-export 100.00% <ø> (ø)
frontend-local-auth 100.00% <ø> (ø)
frontend-manage-roles 63.33% <ø> (ø)
frontend-manage-users 59.81% <ø> (ø)
frontend-report 100.00% <ø> (ø)

Flags with carried forward coverage won't be shown. Click here to find out more.

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

@andrewbrazzatti andrewbrazzatti merged commit 38fd3bb into master Jul 30, 2024
6 of 7 checks passed
andrewbrazzatti added a commit that referenced this pull request Aug 1, 2024
…lone as the existing subscribers are not cleared by the clone. (#2300)
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.

1 participant