Undefined fieldWeight throws an error during complexity anlaysis

[shalarewicz]

If the fieldWeight is undefined during complexity analysis then an unhandled error is thrown. These errors should be handled in development environments to provide clarity on why the fieldWeight is undefined. Production environments should attempt to default to a logical complexity value.

[evanmcneely]

Reassess this after updates to code base in PR #66

[shalarewicz]

After the refactor in #66, this occurs if an invalid parentName is provided when obtaining a resolvedTypeName in the fieldNode function. Temporarily fixing this in work on #44 by throwing an error if the parentName doesn't exist on typeWeights either due to capitalization or an invalid query (the latter case should be caught during schema validation).

We'll need to decide on how to handle this in a production environment.