Decide how to handle QueryPointResultType QueryResultRowType subtype

[gajus]

QueryPointResultType is resulting it loads of errors throughout the codebase warning about attempts to cast an object into a string, e.g.

node_modules/mightyql/dist/types.js.flow:21
 21: type QueryPointResultType = {|
                                 ^ object type. This type cannot be added to
 78:     const fuzzyAddressMatch = _.first(fuseUsingAddress.search(venueDetails.street + ', ' + venueDetails.postcode));
                                                                   ^^^^^^^^^^^^^^^^^^^^^^^^^^ string. See: src/bin/commands/update-venue-google-place-id.js:78

node_modules/mightyql/dist/types.js.flow:21
 21: type QueryPointResultType = {|
                                 ^ object type. This type cannot be added to
 78:     const fuzzyAddressMatch = _.first(fuseUsingAddress.search(venueDetails.street + ', ' + venueDetails.postcode));
                                                                                         ^^^^ string. See: src/bin/commands/update-venue-google-place-id.js:78


Found 3 errors

venueDetails is an instance of QueryResultRowType.

This is a valid error... technically venueDetails.street can be an object. Though guarding against every possible case as such is adding way too much boilerplate code.

[gajus]

Considering how rare QueryPointResultType, I am inclined to remove this annotation at the moment, in favour of explicitly casting QueryResultRowType into QueryPointResultType-capable when required.