Simplify Tracker to use Boolean as state #740
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Until now, a tracker could distinguish several different transactions that could be passed as a parameter to the
track
function. This rarely needed functionality can be implemented by using multiple trackers (whosedata
streams can be combined if needed). This can significantly simplify the tracker's implementation.Specifying a transaction as a parameter of
track
is no longer possible. Appropriately, nodefaultTransaction
can be defined in the factory either. Likewise, the possibility to get a flow, which checks whether a certain transaction is running, by invoking theTracker
is omitted.Solves #736