FieldResolver populates already populated fields

[HarishTeens]

Whenever a field resolver tries to populate an already populated nested field, it throws a "Maximum Call size exceeded Error".

Steps to reproduce

• generate JWT of a new user
• use authUser mutation and request for clubAccess

Fix

The field resolvers should be intelligent enough not to populate the already populated objects which not only would avoid the error, but also helps the datasources send in the populated nested field if it already has it.

[HarishTeens]

Exploring ways of resolving this with dataloaders