use .template.js extension for list messages init resolver

aws-amplify · Oct 3, 2024 · 5ef6f3a · 5ef6f3a
1 parent 2d7dd71
commit 5ef6f3a
Show file tree

Hide file tree

Showing 2 changed files with 2 additions and 2 deletions.
diff --git a/...solvers/list-messages-init-resolver-fn.js → ...ist-messages-init-resolver-fn.template.js b/...solvers/list-messages-init-resolver-fn.js → ...ist-messages-init-resolver-fn.template.js
diff --git a/...ges/amplify-graphql-conversation-transformer/src/resolvers/list-messages-init-resolver.ts b/...ges/amplify-graphql-conversation-transformer/src/resolvers/list-messages-init-resolver.ts
@@ -10,7 +10,7 @@ import { ConversationDirectiveConfiguration } from '../grapqhl-conversation-tran
  * @returns {MappingTemplateProvider}
  */
 export const listMessageInitMappingTemplate = (config: ConversationDirectiveConfiguration): MappingTemplateProvider => {
- const resolver = fs.readFileSync(path.join(__dirname, 'list-messages-init-resolver-fn.js'), 'utf8');
- const templateName = `Query.${config.field.name.value}.list-message-init.js`;
+ const resolver = fs.readFileSync(path.join(__dirname, 'list-messages-init-resolver-fn.template.js'), 'utf8');
+ const templateName = `Query.${config.field.name.value}.list-messages-init.js`;
  return MappingTemplate.s3MappingFunctionCodeFromString(resolver, templateName);
 };