fix(workflow): Do not appear to support conflict policy for child workflows (temporalio#1649)

Author: dandavison

packages/test/src/test-interface-type-safety.ts

@@ -8,6 +8,7 @@ import {
   ChildWorkflowHandle,
   Workflow,
   defineUpdate,
+  ChildWorkflowOptions,
 } from '@temporalio/workflow';
 import { WorkflowHandle, WorkflowUpdateStage } from '@temporalio/client';
 
@@ -181,3 +182,11 @@ test('startUpdate and executeUpdate call signatures', async (t) => {
   }
   t.pass();
 });
+
+test('ChildWorkflowOptions workflowIdConflictPolicy', (t) => {
+  const options: ChildWorkflowOptions = {
+    // @ts-expect-error: workflowIdConflictPolicy is not a valid option
+    workflowIdConflictPolicy: 'USE_EXISTING',
+  };
+  t.pass();
+});

packages/workflow/src/interfaces.ts

@@ -412,7 +412,7 @@ export const [encodeParentClosePolicy, decodeParentClosePolicy] = makeProtoEnumC
   'PARENT_CLOSE_POLICY_'
 );
 
-export interface ChildWorkflowOptions extends CommonWorkflowOptions {
+export interface ChildWorkflowOptions extends Omit<CommonWorkflowOptions, 'workflowIdConflictPolicy'> {
   /**
    * Workflow id to use when starting. If not specified a UUID is generated. Note that it is
    * dangerous as in case of client side retries no deduplication will happen based on the