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
The knockout es5 plugin creates a knockout.computed behind the scenes when we call knockout.defineProperty. This computed listens to observables indefinitely unless we call knockout.getObservable(this, propertyName).dispose(). This should be done in the destroy function for our widgets.
The text was updated successfully, but these errors were encountered:
Thanks. You should probably report a bug on their repository and verify that what you're suggesting is the correct fix. I totally buy that what you're suggesting is needed, but we shouldn't let issues/bugs go unreported for the libraries we use.
I don't know if it's really a bug on their end. It's the same as us recognizing that we need to dispose on subscriptions when our classes are destroyed
Given that we're likely to move away from knockout in the future, this is unlikely to become a priority anytime soon. We'd still happily accept a PR addressing this issue. But tracking this isn't particularly useful because of its low priority, so I will close it. Thanks!
The knockout es5 plugin creates a
knockout.computed
behind the scenes when we callknockout.defineProperty
. Thiscomputed
listens to observables indefinitely unless we callknockout.getObservable(this, propertyName).dispose()
. This should be done in thedestroy
function for our widgets.The text was updated successfully, but these errors were encountered: