Squash changeset on feature/conversation-handler branch and fix api c…

…heck (#1949)

* squash changeset

* fix api check

* grrr

.changeset/blue-tigers-cover.md

@@ -1,5 +1,8 @@
 ---
-'@aws-amplify/ai-constructs': patch
+'@aws-amplify/ai-constructs': minor
+'@aws-amplify/backend-ai': minor
+'@aws-amplify/backend-function': patch
+'@aws-amplify/platform-core': minor
 ---
 
-Add Bedrock tools to conversation handler
+Add new @aws-amplify/ai-constructs and @aws-amplify/backend-ai packages with a conversation handler.

packages/backend-ai/API.md

@@ -18,15 +18,15 @@ declare namespace __export__conversation {
 }
 export { __export__conversation }
 
-declare namespace __export__conversation_runtime {
+declare namespace __export__conversation__runtime {
     export {
         ToolResultContentBlock,
         ExecutableTool,
         ConversationTurnEvent,
         handleConversationTurnEvent
     }
 }
-export { __export__conversation_runtime }
+export { __export__conversation__runtime }
 
 // @public (undocumented)
 type ConversationTurnEvent = runtime.ConversationTurnEvent;

packages/backend-ai/src/index.internal.ts

@@ -2,12 +2,12 @@
 // eslint-disable-next-line @typescript-eslint/naming-convention
 import * as __export__conversation from './conversation/index.js';
 // eslint-disable-next-line @typescript-eslint/naming-convention
-import * as __export__conversation_runtime from './conversation/runtime/index.js';
+import * as __export__conversation__runtime from './conversation/runtime/index.js';
 
 /*
  Api-extractor does not ([yet](https://github.com/microsoft/rushstack/issues/1596)) support multiple package entry points
  Because this package has a submodule export, we are working around this issue by including that export here and directing api-extract to this entry point instead
  This allows api-extractor to pick up the submodule exports in its analysis
  */
 
-export { __export__conversation, __export__conversation_runtime };
+export { __export__conversation, __export__conversation__runtime };

scripts/components/api-changes-validator/import_statements_renderer.ts

@@ -41,8 +41,19 @@ export class ImportStatementsRenderer {
            To work around this we use 'index.internal.ts' files where we export entry points as namespaces.
            Api validator uses special naming convention for these special exports and converts them into start imports
            so that they look like imported namespace.
+
+           The convention in 'index.internal.ts' files is as follows.
+           Assume that package exports 'someEntryPoint/someSubEntryPoint' pointing to 'someSubEntryPoint.js' (arbitrary file).
+           'index.internal.ts' should:
+           1. 'import * as __exports__someEntryPoint__someSubEntryPoint from './someSubEntryPoint.js'
+           2. export { __exports__someEntryPoint__someSubEntryPoint }
+           3. Where:
+              1. __exports__ indicates this workaround to our tooling (e.g. this code)
+              2. __ is a convention to express nesting and is translated to /
          */
-        const entryPointPath = namespaceName.replace('__export__', '');
+        const entryPointPath = namespaceName
+          .replace('__export__', '') // strip prefix
+          .replaceAll('__', '/'); // replace __ with /
         importStatements.push(
           `import * as ${namespaceName} from '${this.packageName}/${entryPointPath}';`
         );

scripts/components/api-changes-validator/test-resources/test-projects/without-breaks/project-with-namespace/API.md

@@ -46,4 +46,14 @@ declare namespace __export__other_entry_point {
   }
 }
 
+export type SomeTypeUnderNestedEntryPoint = {
+  somePropertyUnderNestedEntryPoint: string;
+}
+
+declare namespace __export__other_entry_point__some_nested_entry_point {
+  export {
+    SomeTypeUnderNestedEntryPoint
+  }
+}
+
 ```

scripts/components/api-changes-validator/test-resources/test-projects/without-breaks/project-with-namespace/package.json

@@ -11,6 +11,11 @@
       "import": "./lib/some_other_entry_point.js",
       "require": "./lib/some_other_entry_point.js",
       "types": "./lib/some_other_entry_point.d.ts"
+    },
+    "./other_entry_point/some_nested_entry_point": {
+      "import": "./lib/some_nested_entry_point.js",
+      "require": "./lib/some_nested_entry_point.js",
+      "types": "./lib/some_nested_entry_point.d.ts"
     }
   },
   "types": "lib/index.d.ts"

scripts/components/api-changes-validator/test-resources/test-projects/without-breaks/project-with-namespace/src/some_nested_entry_point.ts

@@ -0,0 +1,3 @@
+export type SomeTypeUnderNestedEntryPoint = {
+  somePropertyUnderNestedEntryPoint: string;
+};