Enable using scope.filteringPath() multiple times per scope

[martinalbert]

Context

I would like to use filteringPath() function multiple times per scope to filter multiple sensitive information from path, that are processed in different places of code. ( I also opened issue about matching recordings #2230, but filtering scopes solved it unless someone wants to use filtering multiple times ).

Every time scope.filteringPath() would be used, it would save filtered path, and work with transformed path in the next call.

Alternatives

I can merge these filtering functions and use it once, but users who uses our library will be able to filter his own information in recordings so if they use it, they would have to filter all credentials that we filter as well.

Has the feature been requested before?

No

If the feature request is accepted, would you be willing to submit a PR?

Yes

[gr2m]

Would you mind sharing some code to demonstrate how the feature would look like compared to today?

our library

What's your library?

[martinalbert]

I've solve this by processing recordings before defining them and therefore not work with already defined scopes, but before, I was hoping it would be storing the state of filtered path once used, so in

scope.filteringPath('search', 'placeholder');
...
scope.filteringPath('another-search', 'placeholder')

scope after first call would replace 'search' for 'placeholder' in path and in second call, filtering would work with already replaced 'search' in path and add filtering on top of it