On extension update, the newest subscription information should be added to core.
Background
With the new way of handling subscriptions in MV3 we need to make sure that we handle update/upgrade scenarios.
Specifically, this means when the scripts are run the SDK based on that configuration should always have the newest data. That means any new filters that got added to or removed from the subscription should reflect. Also, if any subscriptions are no longer supported.
Testing it is difficult at the moment. The SDK needs a mechanism to test "Update" scenarios. This is related to the subscription efforts in #305 (closed).
In adblockpluschrome this idea was attempted here: eyeo/adblockplus/adblockpluschrome!290 (diffs)
Use case
Have a mechanism for having the latest Have a test that confirms that the most recent version of any active subscriptions are available when the SDK starts. This will be very relevant for user migration.
What to change
Implement a testing mechanism that can support checking what happens when a different configuration is provided to an existing SDK instance.
Tests to add
-
does not remove still supported subscriptions on webext release -
does not enable disabled subscriptions on webext release -
removes no longer supported subscriptions on webext release