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’ve noticed that the CancellationTokenSource property in AsyncRelayCommand is never disposed, which might lead to potential resource leaks. I couldn’t find any related discussions in the issue tracker, so I’m wondering if this is intentional or if it could be an area for improvement.
If this is the expected behavior, are there any recommended alternatives for ensuring that the CancellationTokenSource is properly cleaned up? Thanks!
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
I’ve noticed that the CancellationTokenSource property in AsyncRelayCommand is never disposed, which might lead to potential resource leaks. I couldn’t find any related discussions in the issue tracker, so I’m wondering if this is intentional or if it could be an area for improvement.
If this is the expected behavior, are there any recommended alternatives for ensuring that the CancellationTokenSource is properly cleaned up? Thanks!
Beta Was this translation helpful? Give feedback.
All reactions