Stop Disabling Provider Plugin When QueuedTracking Is Enabled #312
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.
Description
Fixes #136
Historically, QueuedTracking disabled the Provider plugin because provider lookups were slow when executed during the tracking request. That context has changed.
The plugin was not enabled by default in core and had to be enabled. Provider plugin is no longer part of core and must be explicitly installed from the Marketplace. When a user installs and enables the plugin, it’s a strong signal that they want provider data.
QueuedTracking’s blanket disabling of Provider leads to unexpected missing data for users who clearly opted in.
Additionally, performance concerns are no longer a good reason to disable the plugin:
Given these points, there’s no longer a justification for QueuedTracking to disable Provider automatically. This PR removes that behavior so users get the data they explicitly enabled.
Issue No
Fixes #136
Checklist