Add operation to main.tsp for testing

Author: FionaBronwen

packages/graphql/package.json

@@ -58,11 +58,11 @@
   "peerDependencies": {
     "@typespec/compiler": "workspace:~",
     "@typespec/emitter-framework": "^0.5.0",
-    "@typespec/http": "workspace:~"
+    "@typespec/http": "workspace:~",
+    "@typespec/mutator-framework": "workspace:~"
   },
   "devDependencies": {
     "@types/node": "~22.13.13",
-    "@typespec/mutator-framework": "workspace:~",
     "rimraf": "~6.0.1",
     "source-map-support": "~0.5.21",
     "typescript": "~5.8.2",

packages/graphql/src/registry.ts

@@ -9,25 +9,28 @@ import {
 } from "graphql";
 import { type TypeKey } from "./type-maps.js";
 import { EnumTypeMap, ModelTypeMap } from "./type-maps/index.js";
-
 /**
  * GraphQLTypeRegistry manages the registration and materialization of TypeSpec (TSP)
  * types into their corresponding GraphQL type definitions.
  *
  * The registry operates in a two-stage process:
  * 1. Registration: TSP types (like Enums, Models, etc.) are first registered
  *    along with relevant metadata (e.g., name, usage flags). This stores an
- *    intermediate representation without immediately creating GraphQL types.
+ *    intermediate representation (`TSPTypeContext`) without immediately creating
+ *    GraphQL types. This stage is typically performed while traversing the TSP AST.
+ *    Register type by calling the appropriate method (e.g., `addEnum`).
  *
  * 2. Materialization: When a GraphQL type is needed (e.g., to build the final
- *    schema or resolve a field type), the registry materializes the TSP type
+ *    schema or resolve a field type), the registry can materialize the TSP type
  *    into its GraphQL counterpart (e.g., `GraphQLEnumType`, `GraphQLObjectType`).
+ *    Materialize types by calling the appropriate method (e.g., `materializeEnum`).
  *
  * This approach helps in:
  *  - Decoupling TSP AST traversal from GraphQL object instantiation.
  *  - Caching materialized GraphQL types to avoid redundant work and ensure object identity.
  *  - Handling forward references and circular dependencies, as types can be
- *    registered first and materialized later when all dependencies are known.
+ *    registered first and materialized later when all dependencies are known or
+ *    by using thunks for fields/arguments.
  */
 export class GraphQLTypeRegistry {
   // TypeMaps for each type kind
@@ -37,9 +40,6 @@ export class GraphQLTypeRegistry {
   // Track all registered names to detect cross-TypeMap name collisions
   private allRegisteredNames = new Set<string>();
 
-  /**
-   * Register a TypeSpec Enum for later materialization.
-   */
   addEnum(tspEnum: Enum): void {
     const enumName = tspEnum.name;
 
@@ -81,9 +81,6 @@ export class GraphQLTypeRegistry {
     return this.modelTypeMap.get(modelName as TypeKey);
   }
 
-  /**
-   * Build the final GraphQL schema configuration.
-   */
   materializeSchemaConfig(): GraphQLSchemaConfig {
     // Collect all materialized types from all TypeMaps
     const allMaterializedGqlTypes: GraphQLNamedType[] = [
@@ -92,7 +89,6 @@ export class GraphQLTypeRegistry {
     ];
     // TODO: Query type will come from operations
     let queryType: GraphQLObjectType | undefined = undefined;
-
     if (!queryType) {
       queryType = new GraphQLObjectType({
         name: "Query",

packages/graphql/test/main.tsp

@@ -25,5 +25,6 @@ namespace MyLibrary {
     Fantasy,
   }
 
+  op getBooks(): Book[];
   op createBook(book: Book): Book;
 }