Listener stacking / chaining API about gherkin2

[aslakhellesoy]

Chaining listeners is definitely powerful. Kind of like the java.io.Writer hierarchy. This is a design issue for individual listeners (some being able to take another one in the constructor).

I'm not sure I need a special API for it though. Do you have a concrete case?

[msassak]

I was thinking of chaining filters: rather than having a single filter that handles tags, lines and names, there could be three that could be applied selectively, reducing the amount of state needed in each filter. But like you said, that doesn't necessarily require a special API.

[aslakhellesoy]

That's a brilliant idea! TagFilter, LineFilter and NameFilter? Sounds a lot cleaner than an intermediary model. Let's try that!

[aslakhellesoy]

Turned out the hard parts were elsewhere, so this isn't needed. Good idea though.