@powerhousedao/academy 4.1.0-dev.18 → 4.1.0-dev.19

package/CHANGELOG.md

@@ -1,3 +1,13 @@
+## 4.1.0-dev.19 (2025-08-14)
+
+### 🩹 Fixes
+
+- **academy:** subgraph example ([ae3e24458](https://github.com/powerhouse-inc/powerhouse/commit/ae3e24458))
+
+### ❤️ Thank You
+
+- Frank
+
 ## 4.1.0-dev.18 (2025-08-14)
 
 This was a version bump only for @powerhousedao/academy to align it with other projects, there were no code changes.

package/docs/academy/02-MasteryTrack/04-WorkWithData/03-UsingSubgraphs.md

@@ -78,7 +78,7 @@ Initializing Subgraph Manager...
   ➜  Reactor:   http://localhost:4001/d/powerhouse
 ```
 
-## 2. Building a to-do list subgraph
+## 2. Building a search subgraph
 
 Now that we've generated our subgraph its tome to define the GraphQL schema and implement the resolvers.
 
@@ -118,7 +118,7 @@ export const getResolvers = (subgraph: Subgraph) => {
         const todoItems: string[] = [];
         for (const docId of documents) {
           const doc: ToDoListDocument = await reactor.getDocument(docId);
-          if (doc.header.documentType !== "powerhouse/todo-list") {
+          if (doc.header.documentType !== "powerhouse/todolist") {
             continue;
           }
 
@@ -153,7 +153,12 @@ You should see the subgraph being registered in the console output:
 ### 3.2. Create some test data
 Before testing queries, let's create some To-do List documents with test data:
 
-1. Open Connect at `http://localhost:3001` in another terminal
+1. Start Connect 
+```bash
+ph connect
+```
+
+1. Open Connect at `http://localhost:3000` in the browser
 2. Add the 'remote' drive that is running locally via the (+) 'Add Drive' button. Add 'http://localhost:4001/d/powerhouse'
 3. Create a new To-do List document
 4. Add some test items:
@@ -165,7 +170,7 @@ Before testing queries, let's create some To-do List documents with test data:
 Open your browser and go to:
 
 ```bash
-http://localhost:4001/graphql/to-do-list
+http://localhost:4001/graphql
 ```
 
 ### 3.4. Test the queries
@@ -173,10 +178,11 @@ http://localhost:4001/graphql/to-do-list
 **Query 1: Search for Todos **
 ```graphql
 query {
-  searchTodos(driveId: "powerhouse", searchTerm: "test")
+  searchTodos(driveId: "powerhouse", searchTerm: "Test")
 }
 ```
 
+You should get a list of the document Ids which contain the search term "Test".
 
 ### 3.5. Test real-time updates
 
@@ -190,9 +196,10 @@ To verify that your subgraph stays synchronized with document changes:
 
 This demonstrates the real-time synchronization between the document model and the subgraph through event processing.
 
-## 4. Working with the supergraph or gateway
 
-A supergraph is a GraphQL schema that combines multiple underlying GraphQL APIs, known as subgraphs, into a single, unified graph. This architecture allows different teams to work independently on their respective services (subgraphs) while providing a single entry point for clients or users to query all available data.
+## 4. Working with the GraphQL Gateway
+
+The GraphQL Gateway is a GraphQL schema that combines multiple underlying GraphQL APIs, known as subgraphs, into a single, unified graph. This architecture allows different teams to work independently on their respective services (subgraphs) while providing a single entry point for clients or users to query all available data.
 
 ### 4.1 Key concepts
 

package/docs/academy/02-MasteryTrack/04-WorkWithData/05-RelationalDbProcessor.md

@@ -268,19 +268,41 @@ A subgraph is a GraphQL schema that exposes your processed data to clients. It:
 
 ### Configure the Subgraph
 
-Open `./subgraphs/todo/index.ts` and configure the resolvers:
+Open `./subgraphs/todo/schema.ts`and configure the schema:
 
 ```ts
-import { Subgraph } from "@powerhousedao/reactor-api";
 import { gql } from "graphql-tag";
+import type { DocumentNode } from "graphql";
+
+export const schema: DocumentNode = gql`
+
+# Define the structure of a todo item as returned by GraphQL
+type ToDoListEntry {
+  task: String!     # The task description (! means required/non-null)
+  status: Boolean!  # The completion status (true = done, false = pending)
+}
+
+# Define available queries
+type Query {
+  todos(driveId: ID!): [ToDoListEntry]  # Get array of todos for a specific drive
+}
+`;
+
+```
+
+Open `./subgraphs/todo/resolvers.ts` and configure the resolvers:
+
+```ts
+// subgraphs/search-todos/resolvers.ts
+import { type Subgraph } from "@powerhousedao/reactor-api";
+import { type ToDoListDocument } from "document-models/to-do-list/index.js";
 import { TodoIndexerProcessor } from "../../processors/todo-indexer/index.js";
 
-export class TodoSubgraph extends Subgraph {
-  // Human-readable name for this subgraph
-  name = "Todos";
+export const getResolvers = (subgraph: Subgraph) => {
+  const reactor = subgraph.reactor;
+  const relationalDb = subgraph.relationalDb;
 
-  // GraphQL resolvers - functions that fetch data for each field
-  resolvers = {
+  return {
     Query: {
       todos: {
         // Resolver function for the "todos" query
@@ -288,7 +310,7 @@ export class TodoSubgraph extends Subgraph {
         resolve: async (_: any, args: {driveId: string}) => {
           // Query the database using the processor's static query method
           // This gives us access to the namespaced database for the specific drive
-          const todos = await TodoIndexerProcessor.query(args.driveId, this.relationalDb)
+          const todos = await TodoIndexerProcessor.query(args.driveId, relationalDb)
             .selectFrom("todo")        // Select from the "todo" table
             .selectAll()              // Get all columns
             .execute();               // Execute the query
@@ -302,29 +324,10 @@ export class TodoSubgraph extends Subgraph {
       },
     },
   };
-
-  // GraphQL schema definition using GraphQL Schema Definition Language (SDL)
-  typeDefs = gql`
-
-  # Define the structure of a todo item as returned by GraphQL
-  type ToDoListEntry {
-    task: String!     # The task description (! means required/non-null)
-    status: Boolean!  # The completion status (true = done, false = pending)
-  }
-
-  # Define available queries
-  type Query {
-    todos(driveId: ID!): [ToDoListEntry]  # Get array of todos for a specific drive
-  }
-  `;
-
-  // Cleanup method called when the subgraph disconnects
-  async onDisconnect() {
-    // Add any cleanup logic here if needed
-  }
-}
+};
 ```
 
+
 ## Now query the data via the supergraph.
 
 **Understanding the Supergraph**

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@powerhousedao/academy",
-  "version": "4.1.0-dev.18",
+  "version": "4.1.0-dev.19",
   "homepage": "https://powerhouse.academy",
   "repository": {
     "type": "git",