Pattern for allowing for subsequent network intercepts when using blocklist functionality

[nickblumenthal]

Is there a good convention that allows for us to utilize both the blocklist functionality of ferrum and a subsequent network request intercept? Our use case is that we have a generic list of blocklisted urls and then we want to spoof specific browser side network requests. However, it appears that when we register the blocklist, the subsequent subscription ends in behavior that ultimately aborts or continues the request regardless of the number of subscribers for the Fetch.requestPaused event.

I threw together a branch that demonstrates the behavior I'm looking for but I think I might be missing something obvious. The other pattern I could see is setting some sort of third instance variable on the network, i.e. @intercepted_urls and then matching on that in both the blocklist/whitelist paths.

Thanks in advance for the insights!