Support filter management in an mv3 context
Background
We need to support the various functions available in the current SDK in the context of MV3. Initially, we were concerned with breaking changes but updating the existing functions to be asynchronous is not a problem.
Use case
Managing user filters on a V3 context.
What to change
-
Update the add
,remove
, andgetUserFilters
to work in the context of mv3 (!238 (merged)) -
Handling enable / disable filters on DNR rules, including adding request-filter tests on that. That will need removing disabled filters from the DNR, and add them again when enabled back (!244 (merged)) -
Checking the integrity between local storage and the existing DNR rules (the "UUID" mechanism on the V3 prototype) -
Filter events (!248 (merged)) -
Move dynamicFilters
from local storage intoindexedDB
(!254 (merged))
Edited by Toni Feliu