You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I'm not set up to run it locally for tests ( or even how it is set up here).
An open question also would be about the potential use cases with custom renderers that may extend this and use this.subscription for other observables.
It likely needs a separate property to ensure it's backwards compatible.
Previously, the subscription to the jsonForm state in Angular was never unsubscribed.
With this commit, all subscriptions will be unsubscribed when the component is destroyed.
Closeseclipsesource#2354
)
Previously, subscriptions to the JSON Forms state in Angular were never removed when renderer components are destroyed.
With this commit, all subscriptions will be unsubscribed when the component is destroyed.
The base renderer offers an addSubscription method to register one or multiple subscriptions
to automatically be unsubscribed on destroy. With this, extending renderers do not need to
implement the unsubscribe again.
Closes#2354
Co-authored-by: Lucas Koehler <lkoehler@eclipsesource.com>
Describe the bug
https://github.com/eclipsesource/jsonforms/blob/master/packages/angular/src/library/abstract-control.ts
ngOnDestroy does unsubscribe, but this.jsonFormsService.$state.subscribe is never actually assigned to the variable.
So every schema change adds new subscriptions and old ones still remain active and trigger.
Expected behavior
removed controls are unsubscribed
Steps to reproduce the issue
Screenshots
No response
Which Version of JSON Forms are you using?
3.3.0
Framework
Angular
RendererSet
Other (please specify in the Additional context field)
Additional context
No response
The text was updated successfully, but these errors were encountered: