fix(models): support legacy article & article replies

- Their createdAt are null, so the field should be nullable.
cofacts · Oct 25, 2023 · ff17420 · ff17420
1 parent 3a215c4
commit ff17420
Show file tree

Hide file tree

Showing 2 changed files with 8 additions and 2 deletions.
diff --git a/src/graphql/models/Article.js b/src/graphql/models/Article.js
@@ -61,7 +61,10 @@ const Article = new GraphQLObjectType({
   fields: () => ({
     id: { type: new GraphQLNonNull(GraphQLID) },
     text: { type: GraphQLString },
-    createdAt: { type: new GraphQLNonNull(GraphQLString) },
+    createdAt: {
+      type: GraphQLString,
+      description: 'May be null for legacy articles',
+    },
     updatedAt: { type: GraphQLString },
     status: { type: new GraphQLNonNull(ReplyRequestStatusEnum) },
     references: { type: new GraphQLList(ArticleReference) },

diff --git a/src/graphql/models/ArticleReply.js b/src/graphql/models/ArticleReply.js
@@ -134,7 +134,10 @@ export default new GraphQLObjectType({
       resolve: ({ status }) => (status === undefined ? 'NORMAL' : status),
     },
 
-    createdAt: { type: new GraphQLNonNull(GraphQLString) },
+    createdAt: {
+      type: GraphQLString,
+      description: 'May be null for legacy articles',
+    },
     updatedAt: { type: GraphQLString },
   }),
 });