Fix apollo-server null issue due to missing columns

Recent apollo-server-core changes always define a field resolver (see the enablePluginsForSchemaResolvers function, apollo-server issue #3988) so '!field.resolve' is not a good check for columns. Instead use parentTypeNode.constructor.name.

Incremented release version and updated change log.

docs/CHANGELOG.md

@@ -1,3 +1,9 @@
+### v3.0.2 (April 4, 2021)
+
+#### Fixed
+
+- Fix apollo-server null issue due to missing columns [#444](https://github.com/join-monster/join-monster/pull/444)
+
 ### v3.0.0
 
 **Breaking changes:**

package.json

@@ -1,6 +1,6 @@
 {
   "name": "join-monster",
-  "version": "3.0.1",
+  "version": "3.0.2",
   "description": "A GraphQL to SQL query execution layer for batch data fetching.",
   "main": "dist/index.js",
   "engines": {

src/query-ast-to-sql-ast/index.js

@@ -235,20 +235,23 @@ export function populateASTNode(
       aliasFrom += '@' + parentTypeNode.name
     }
     sqlASTNode.as = namespace.generate('column', aliasFrom)
-    // is it just a column? if they specified a sqlColumn or they didn't define a resolver, yeah
-  } else if (fieldConfig.sqlColumn || !field.resolve) {
+    // or maybe it just depends on some SQL columns
+  } else if (fieldConfig.sqlDeps) {
+    sqlASTNode.type = 'columnDeps'
+    sqlASTNode.names = fieldConfig.sqlDeps
+    // is it just a column? if they specified a sqlColumn or parentTypeNode is a GraphQLObjectType, yeah
+    // recent apollo-server-core always define a field resolver
+    // see enablePluginsForSchemaResolvers function: apollo-server issue #3988)
+  } else if (fieldConfig.sqlColumn ||
+    ['GraphQLObjectType', 'GraphQLInterfaceType'].includes(parentTypeNode.constructor.name)
+  ) {
     sqlASTNode.type = 'column'
     sqlASTNode.name = fieldConfig.sqlColumn || field.name
     let aliasFrom = (sqlASTNode.fieldName = field.name)
     if (sqlASTNode.defferedFrom) {
       aliasFrom += '@' + parentTypeNode.name
     }
     sqlASTNode.as = namespace.generate('column', aliasFrom)
-    // or maybe it just depends on some SQL columns
-  } else if (fieldConfig.sqlDeps) {
-    sqlASTNode.type = 'columnDeps'
-    sqlASTNode.names = fieldConfig.sqlDeps
-    // maybe this node wants no business with your SQL, because it has its own resolver
   } else {
     sqlASTNode.type = 'noop'
   }

test-api/schema-basic/User.js

@@ -247,6 +247,11 @@ const User = new GraphQLObjectType({
     },
     favNums: {
       type: new GraphQLList(GraphQLInt),
+      extensions: {
+        joinMonster: {
+          ignoreAll: true
+        }
+      },
       resolve: () => [1, 2, 3]
     },
     numLegs: {