The previous approach had a problem: if the view scope is cancelled, the handling of on-going events was cancelled even if the mvflow scope was not cancelled.
This PR introduces (breaking) changes to the API so we are able to distinguish the scope of the view and that of the mvflow.
The previous approach had a problem: if the view scope is cancelled, the handling of on-going events was cancelled even if the mvflow scope was not cancelled.
This PR introduces (breaking) changes to the API so we are able to distinguish the scope of the view and that of the mvflow.