Thank you for your contribution.

Unfortunately I don't think we want to go down the route of per-format annotations, duplicating all functionality.

So while the idea of having a mechanism for annotating different behavior for different format is valid, we need to figure out more maintainable approach.

Hi@cowtowncoder !
You absolutely true about new mechanism, but I don't see any other way for branch 2.x. Therefore I suggest stay this change in 2.x branch only and use this case (different incluthion rules for different output formats) when develop new approach.

Thanks.

Hi@cowtowncoder ! You absolutely true about new mechanism, but I don't see any other way for branch 2.x. Therefore I suggest stay this change in 2.x branch only and use this case (different incluthion rules for different output formats) when develop new approach.

Thanks.

@IMurzich 2.x is no longer the dev branch. Most changes that will go in 2.x in future will be bug fixes. This is not a bug fix.

Ok, will I move this change to 3.x branch?

@cowtowncoder , thank you for your time.