How do you structure the the context object described here in such a way that it doesn't contain every service that your schema may need?
In the example StarWars schema all fields use the same context (CharacterRepo) to resolve.
My context could potentially contain 50 different services?