Disable trackers in commands that don't need them #1190
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.
Motivation
Related to: #1181
Most of our commands don't need the overhead of Tapioca runtime trackers constantly running in the background and doing processing. This PR implements and makes use of a mechanism to disable all trackers for commands that don't need them.
Implementation
Tracker
module that is responsible for registration and disabling of an individual tracker module.Tracker
module and respect theenabled?
state.CommandWithoutTracker
base class that disables all trackers during initialization.GemCommand
) subclass fromCommandWithoutTracker
.Tests
No added tests.