(@graphql-tools/resolvers-composition) - defining resolvers pipeline for multiply fields

[eKulshan]

Hello!
I've been trying to move from directives in the schema to resolvers composition for simplification and easiness.
Example in documentation claims that I can use glob matching pattern to be able to define multiple fields to be affected by same resolver pipeline: Query.{first, second}: [Auth()}
So I assumed I can do something like this: [Mutation.{${UserAccessMutations.join(', ')}}]: [Auth()]
And I've discovered that actually resolver compositions can work with only 2 fields. So if I need more, I should do a lot of code duplication.

This is really not as handy as it may be. Why there is such a limitation? Maybe we can put this as a feature request?

[ardatan]

Would you create a PR with a failing test case? So we can continue from that

[eKulshan]

Gladly! I'm new to opensource and have not much programming experience. I'll look into existing tests as examples and try to come up with my own.
But how should I represent that resolver wasn't applied? Is assert on mappingResult object will be enough?