create-harper 0.11.0 → 0.12.1

package/index.js

@@ -5,7 +5,6 @@ import { helpMessage } from './lib/constants/helpMessage.js';
 import { pkgFromUserAgent } from './lib/pkg/pkgFromUserAgent.js';
 import { checkForUpdate } from './lib/steps/checkForUpdate.js';
 import { getEnvVars } from './lib/steps/getEnvVars.js';
-import { getExamples } from './lib/steps/getExamples.js';
 import { getPackageName } from './lib/steps/getPackageName.js';
 import { getProjectName } from './lib/steps/getProjectName.js';
 import { getRunAppImmediately } from './lib/steps/getRunAppImmediately.js';
@@ -60,11 +59,6 @@ async function init() {
 	if (templateResult.cancelled) { return cancel(); }
 	const { template } = templateResult;
 
-	// Choose which examples to include
-	const examplesResult = await getExamples(template, interactive);
-	if (examplesResult.cancelled) { return cancel(); }
-	const { excludedFiles } = examplesResult;
-
 	// Get environment variables for .env file
 	const envVarsResult = await getEnvVars(interactive, template, args.deploymentUsername, args.deploymentURL);
 	if (envVarsResult.cancelled) { return cancel(); }
@@ -80,7 +74,7 @@ async function init() {
 	// Write out the contents based on all prior steps.
 	const cwd = process.cwd();
 	const root = path.join(cwd, targetDir);
-	scaffoldProject(root, projectName, packageName, template, envVars, excludedFiles);
+	scaffoldProject(root, projectName, packageName, template, envVars);
 
 	// Log out the next steps.
 	installAndOptionallyStart(root, pkgManager, immediate, args.skipInstall);

package/lib/fs/crawlTemplateDir.js

@@ -9,23 +9,16 @@ import { copyFile } from './copyFile.js';
  * @param {string} root - The current target directory.
  * @param {string} dir - The current source directory in the template.
  * @param {Record<string, string> | ((content: string) => string)} substitutions - A mapping of strings to replace or a function that returns the updated content.
- * @param {string[]} [excludedFiles] - A list of relative paths to exclude from copying.
- * @param {string} [templateRootDir] - The absolute path to the root of the template directory (internal).
  */
-export function crawlTemplateDir(root, dir, substitutions, excludedFiles = [], templateRootDir = dir) {
+export function crawlTemplateDir(root, dir, substitutions) {
 	const files = fs.readdirSync(dir);
 	for (const file of files) {
 		const templatePath = path.join(dir, file);
-		const relativePath = path.relative(templateRootDir, templatePath).split(path.sep).join('/');
-
-		if (excludedFiles.includes(relativePath)) {
-			continue;
-		}
 
 		const targetPath = path.join(root, renameFiles[file] ?? file);
 		if (fs.lstatSync(templatePath).isDirectory()) {
 			fs.mkdirSync(targetPath, { recursive: true });
-			crawlTemplateDir(targetPath, templatePath, substitutions, excludedFiles, templateRootDir);
+			crawlTemplateDir(targetPath, templatePath, substitutions);
 		} else {
 			copyFile(templatePath, targetPath, substitutions);
 		}

package/lib/steps/scaffoldProject.js

@@ -12,9 +12,8 @@ import { crawlTemplateDir } from '../fs/crawlTemplateDir.js';
  * @param {string} packageName - The name for the package.json.
  * @param {string} template - The template name to use.
  * @param {import('./getEnvVars.js').EnvVars} [envVars] - Environment variables to substitute.
- * @param {string[]} [excludedFiles] - A list of files to exclude from the template.
  */
-export function scaffoldProject(root, projectName, packageName, template, envVars, excludedFiles = []) {
+export function scaffoldProject(root, projectName, packageName, template, envVars) {
 	fs.mkdirSync(root, { recursive: true });
 	prompts.log.step(`Scaffolding project in ${root}...`);
 
@@ -34,5 +33,5 @@ export function scaffoldProject(root, projectName, packageName, template, envVar
 		'..',
 		`template-${template}`,
 	);
-	crawlTemplateDir(root, templateDir, substitutions, excludedFiles);
+	crawlTemplateDir(root, templateDir, substitutions);
 }

package/package.json

@@ -1,7 +1,7 @@
 {
 	"name": "create-harper",
 	"description": "Scaffold a new Harper project in JavaScript or TypeScript.",
-	"version": "0.11.0",
+	"version": "0.12.1",
 	"type": "module",
 	"author": {
 		"name": "HarperDB",

package/template-react/AGENTS.md

@@ -4,7 +4,7 @@ This repository contains "skills" that guide AI agents in developing Harper appl
 
 ## Available Skills
 
-- [Adding Tables](skills/adding-tables.md): Learn how to define schemas and enable automatic REST APIs for your database tables.
+- [Adding Tables with Schemas](skills/adding-tables-with-schemas.md): Learn how to define schemas and enable automatic REST APIs for your database tables with schema .graphql files in Harper.
 - [Automatic REST APIs](skills/automatic-rest-apis.md): Details on the CRUD endpoints automatically generated for exported tables.
 - [Querying REST APIs](skills/querying-rest-apis.md): How to use filters, operators, sorting, and pagination in REST requests.
 - [Programmatic Table Requests](skills/programmatic-table-requests.md): How to use filters, operators, sorting, and pagination in programmatic table requests.

package/template-react/resources/README.md

@@ -0,0 +1,11 @@
+# Resources
+
+The [schemas you define in .GraphQL files](../skills/adding-tables-with-schemas.md) will [automatically stand-up REST APIs](../skills/automatic-rest-apis.md).
+
+But you can [extend your tables with custom logic](../skills/extending-tables.md) and [create your own resources](../skills/custom-resources.md) in this directory.
+
+## Want to read more?
+
+Check out the rest of the "skills" documentation!
+
+[AGENTS.md](../AGENTS.md)

package/template-react/schemas/README.md

@@ -0,0 +1,11 @@
+# Schemas
+
+Your schemas are defined in `.graphql` files within this `schemas` directory. These files contain the structure and types for your database tables, allowing Harper to automatically generate REST APIs for CRUD operations.
+
+Take a look at the [Adding Tables with Schemas](../skills/adding-tables-with-schemas.md) to learn more!
+
+## Want to read more?
+
+Check out the rest of the "skills" documentation!
+
+[AGENTS.md](../AGENTS.md)

package/template-react-ts/AGENTS.md

@@ -4,7 +4,7 @@ This repository contains "skills" that guide AI agents in developing Harper appl
 
 ## Available Skills
 
-- [Adding Tables](skills/adding-tables.md): Learn how to define schemas and enable automatic REST APIs for your database tables.
+- [Adding Tables with Schemas](skills/adding-tables-with-schemas.md): Learn how to define schemas and enable automatic REST APIs for your database tables with schema .graphql files in Harper.
 - [Automatic REST APIs](skills/automatic-rest-apis.md): Details on the CRUD endpoints automatically generated for exported tables.
 - [Querying REST APIs](skills/querying-rest-apis.md): How to use filters, operators, sorting, and pagination in REST requests.
 - [Programmatic Table Requests](skills/programmatic-table-requests.md): How to use filters, operators, sorting, and pagination in programmatic table requests.

package/template-react-ts/resources/README.md

@@ -0,0 +1,11 @@
+# Resources
+
+The [schemas you define in .GraphQL files](../skills/adding-tables-with-schemas.md) will [automatically stand-up REST APIs](../skills/automatic-rest-apis.md).
+
+But you can [extend your tables with custom logic](../skills/extending-tables.md) and [create your own resources](../skills/custom-resources.md) in this directory.
+
+## Want to read more?
+
+Check out the rest of the "skills" documentation!
+
+[AGENTS.md](../AGENTS.md)

package/template-react-ts/schemas/README.md

@@ -0,0 +1,11 @@
+# Schemas
+
+Your schemas are defined in `.graphql` files within this `schemas` directory. These files contain the structure and types for your database tables, allowing Harper to automatically generate REST APIs for CRUD operations.
+
+Take a look at the [Adding Tables with Schemas](../skills/adding-tables-with-schemas.md) to learn more!
+
+## Want to read more?
+
+Check out the rest of the "skills" documentation!
+
+[AGENTS.md](../AGENTS.md)

package/template-vanilla/AGENTS.md

@@ -4,7 +4,7 @@ This repository contains "skills" that guide AI agents in developing Harper appl
 
 ## Available Skills
 
-- [Adding Tables](skills/adding-tables.md): Learn how to define schemas and enable automatic REST APIs for your database tables.
+- [Adding Tables with Schemas](skills/adding-tables-with-schemas.md): Learn how to define schemas and enable automatic REST APIs for your database tables with schema .graphql files in Harper.
 - [Automatic REST APIs](skills/automatic-rest-apis.md): Details on the CRUD endpoints automatically generated for exported tables.
 - [Querying REST APIs](skills/querying-rest-apis.md): How to use filters, operators, sorting, and pagination in REST requests.
 - [Programmatic Table Requests](skills/programmatic-table-requests.md): How to use filters, operators, sorting, and pagination in programmatic table requests.

package/template-vanilla/resources/README.md

@@ -0,0 +1,11 @@
+# Resources
+
+The [schemas you define in .GraphQL files](../skills/adding-tables-with-schemas.md) will [automatically stand-up REST APIs](../skills/automatic-rest-apis.md).
+
+But you can [extend your tables with custom logic](../skills/extending-tables.md) and [create your own resources](../skills/custom-resources.md) in this directory.
+
+## Want to read more?
+
+Check out the rest of the "skills" documentation!
+
+[AGENTS.md](../AGENTS.md)

package/template-vanilla/schemas/README.md

@@ -0,0 +1,11 @@
+# Schemas
+
+Your schemas are defined in `.graphql` files within this `schemas` directory. These files contain the structure and types for your database tables, allowing Harper to automatically generate REST APIs for CRUD operations.
+
+Take a look at the [Adding Tables with Schemas](../skills/adding-tables-with-schemas.md) to learn more!
+
+## Want to read more?
+
+Check out the rest of the "skills" documentation!
+
+[AGENTS.md](../AGENTS.md)

package/template-vanilla-ts/AGENTS.md

@@ -4,7 +4,7 @@ This repository contains "skills" that guide AI agents in developing Harper appl
 
 ## Available Skills
 
-- [Adding Tables](skills/adding-tables.md): Learn how to define schemas and enable automatic REST APIs for your database tables.
+- [Adding Tables with Schemas](skills/adding-tables-with-schemas.md): Learn how to define schemas and enable automatic REST APIs for your database tables with schema .graphql files in Harper.
 - [Automatic REST APIs](skills/automatic-rest-apis.md): Details on the CRUD endpoints automatically generated for exported tables.
 - [Querying REST APIs](skills/querying-rest-apis.md): How to use filters, operators, sorting, and pagination in REST requests.
 - [Programmatic Table Requests](skills/programmatic-table-requests.md): How to use filters, operators, sorting, and pagination in programmatic table requests.

package/template-vanilla-ts/resources/README.md

@@ -0,0 +1,11 @@
+# Resources
+
+The [schemas you define in .GraphQL files](../skills/adding-tables-with-schemas.md) will [automatically stand-up REST APIs](../skills/automatic-rest-apis.md).
+
+But you can [extend your tables with custom logic](../skills/extending-tables.md) and [create your own resources](../skills/custom-resources.md) in this directory.
+
+## Want to read more?
+
+Check out the rest of the "skills" documentation!
+
+[AGENTS.md](../AGENTS.md)

package/template-vanilla-ts/schemas/README.md

@@ -0,0 +1,11 @@
+# Schemas
+
+Your schemas are defined in `.graphql` files within this `schemas` directory. These files contain the structure and types for your database tables, allowing Harper to automatically generate REST APIs for CRUD operations.
+
+Take a look at the [Adding Tables with Schemas](../skills/adding-tables-with-schemas.md) to learn more!
+
+## Want to read more?
+
+Check out the rest of the "skills" documentation!
+
+[AGENTS.md](../AGENTS.md)

package/lib/constants/exampleFiles.js

@@ -1,33 +0,0 @@
-/**
- * @typedef {Object} ExampleFile
- * @property {string} label - The display label for the example.
- * @property {string} value - The internal value for the example.
- * @property {string[]} files - The files associated with this example.
- */
-
-/**
- * The list of available example files that can be optionally included in the project.
- * @type {ExampleFile[]}
- */
-export const exampleFiles = [
-	{
-		label: 'Table schema',
-		value: 'tableSchema',
-		files: ['schemas/examplePeople.graphql'],
-	},
-	{
-		label: 'Table handling',
-		value: 'table',
-		files: ['resources/examplePeople.ts', 'resources/examplePeople.js'],
-	},
-	{
-		label: 'Resource',
-		value: 'resource',
-		files: ['resources/greeting.ts', 'resources/greeting.js'],
-	},
-	{
-		label: 'Sockets',
-		value: 'socket',
-		files: ['resources/exampleSocket.ts', 'resources/exampleSocket.js'],
-	},
-];

package/lib/steps/getExamples.js

@@ -1,49 +0,0 @@
-import * as prompts from '@clack/prompts';
-import fs from 'node:fs';
-import path from 'node:path';
-import { fileURLToPath } from 'node:url';
-import { exampleFiles } from '../constants/exampleFiles.js';
-
-/**
- * Step 5 (Optional): Choose which example files to include in the project.
- *
- * @param {string} template - The selected template name.
- * @param {boolean} interactive - Whether the CLI is running in interactive mode.
- * @returns {Promise<{excludedFiles: string[], cancelled: boolean}>} - A list of files to exclude based on selection, and cancellation status.
- */
-export async function getExamples(template, interactive) {
-	const templateDir = path.resolve(
-		fileURLToPath(import.meta.url),
-		'..',
-		'..',
-		'..',
-		`template-${template}`,
-	);
-
-	const availableExamples = exampleFiles.filter((example) =>
-		example.files.some((file) => fs.existsSync(path.join(templateDir, file)))
-	);
-
-	if (availableExamples.length === 0 || !interactive) {
-		return { excludedFiles: [], cancelled: false };
-	}
-
-	const selectedExamples = await prompts.multiselect({
-		message: 'Select examples to include:',
-		options: availableExamples.map((example) => ({
-			label: example.label,
-			value: example.value,
-		})),
-		initialValues: availableExamples.map((example) => example.value),
-		required: false,
-	});
-
-	if (prompts.isCancel(selectedExamples)) {
-		return { excludedFiles: [], cancelled: true };
-	}
-
-	const unselectedExamples = availableExamples.filter((example) => !selectedExamples.includes(example.value));
-	const excludedFiles = unselectedExamples.flatMap((example) => example.files);
-
-	return { excludedFiles, cancelled: false };
-}

package/template-react/resources/examplePeople.js

@@ -1,14 +0,0 @@
-import { tables } from 'harperdb';
-
-export class ExamplePeople extends tables.ExamplePeople {
-	// we can define our own custom POST handler
-	post(content) {
-		// do something with the incoming content;
-		return super.post(content);
-	}
-	// or custom GET handler
-	get() {
-		// we can modify this resource before returning
-		return super.get();
-	}
-}

package/template-react/resources/exampleSocket.js

@@ -1,34 +0,0 @@
-import { Resource, tables } from 'harperdb';
-
-export class ExampleSocket extends Resource {
-	static loadAsInstance = false;
-
-	// This customizes handling the socket connections; tables can have this method too!
-	async *connect(
-		target,
-		incomingMessages,
-	) {
-		const subscription = await tables.ExamplePeople.subscribe(target);
-		if (!incomingMessages) {
-			// Server sent events, no incoming messages!
-			// Subscribe to changes to the table.
-			return subscription;
-		}
-		for await (let message of incomingMessages) {
-			const { type, id, name, tag } = message;
-			switch (type) {
-				case 'get':
-					const loaded = await tables.ExamplePeople.get(id);
-					yield {
-						type: 'get',
-						id,
-						...(loaded ? loaded : {}),
-					};
-					break;
-				case 'put':
-					await tables.ExamplePeople.put(id, { name, tag });
-					break;
-			}
-		}
-	}
-}

package/template-react/resources/greeting.js

@@ -1,10 +0,0 @@
-import { Resource } from 'harperdb';
-
-export class Greeting extends Resource {
-	// a "Hello, world!" handler
-	static loadAsInstance = false; // use the updated/newer Resource API
-
-	get() {
-		return { greeting: 'Hello, world!' };
-	}
-}

package/template-react/schemas/exampleCat.graphql

@@ -1,6 +0,0 @@
-## This table is @export'ed, which means API endpoints are stood up for it automatically.
-type ExampleCat @table @export {
-	id: ID @primaryKey # Here we define primary key (must be one)
-	name: String # we can define any other attributes here
-	tag: String @indexed # we can specify any attributes that should be indexed
-}

package/template-react/schemas/examplePeople.graphql

@@ -1,7 +0,0 @@
-## Here we can define any tables in our database. This example shows how we define a type as a table using
-## the type name as the table name and specifying it is an "export" available in the REST and other external protocols.
-type ExamplePeople @table @export {
-	id: ID @primaryKey # Here we define primary key (must be one)
-	name: String # we can define any other attributes here
-	tag: String @indexed # we can specify any attributes that should be indexed
-}

package/template-react-ts/resources/examplePeople.ts

@@ -1,20 +0,0 @@
-import { type RequestTargetOrId, tables } from 'harperdb';
-
-export interface ExamplePerson {
-	id: string;
-	name: string;
-	tag: string;
-}
-
-export class ExamplePeople extends tables.ExamplePeople<ExamplePerson> {
-	// we can define our own custom POST handler
-	async post(target: RequestTargetOrId, newRecord: Omit<ExamplePerson, 'id'>) {
-		// do something with the incoming content;
-		return super.post(target, newRecord);
-	}
-	// or custom GET handler
-	async get(target: RequestTargetOrId): Promise<ExamplePerson> {
-		// we can modify this resource before returning
-		return super.get(target);
-	}
-}

package/template-react-ts/resources/exampleSocket.ts

@@ -1,41 +0,0 @@
-import { type IterableEventQueue, RequestTarget, Resource, tables } from 'harperdb';
-
-interface ExampleSocketRecord {
-	id: string;
-	type?: 'get' | 'put';
-	name: string;
-	tag: string;
-}
-
-export class ExampleSocket extends Resource<ExampleSocketRecord> {
-	static loadAsInstance = false;
-
-	// This customizes handling the socket connections; tables can have this method too!
-	async *connect(
-		target: RequestTarget,
-		incomingMessages: IterableEventQueue<ExampleSocketRecord>,
-	): AsyncIterable<ExampleSocketRecord> {
-		const subscription = await tables.ExamplePeople.subscribe(target);
-		if (!incomingMessages) {
-			// Server sent events, no incoming messages!
-			// Subscribe to changes to the table.
-			return subscription;
-		}
-		for await (let message of incomingMessages) {
-			const { type, id, name, tag } = message;
-			switch (type) {
-				case 'get':
-					const loaded = await tables.ExamplePeople.get(id);
-					yield {
-						type: 'get',
-						id,
-						...(loaded ? loaded : {}),
-					};
-					break;
-				case 'put':
-					await tables.ExamplePeople.put(id, { name, tag });
-					break;
-			}
-		}
-	}
-}

package/template-react-ts/resources/greeting.ts

@@ -1,29 +0,0 @@
-import { type RecordObject, type RequestTargetOrId, Resource } from 'harperdb';
-
-interface GreetingRecord {
-	greeting: string;
-}
-
-export class Greeting extends Resource<GreetingRecord> {
-	static loadAsInstance = false;
-
-	async post(target: RequestTargetOrId, newRecord: Partial<GreetingRecord & RecordObject>): Promise<GreetingRecord> {
-		return { greeting: 'Greetings, post!' };
-	}
-
-	async get(target?: RequestTargetOrId): Promise<GreetingRecord> {
-		return { greeting: 'Greetings, get!' };
-	}
-
-	async put(target: RequestTargetOrId, record: GreetingRecord & RecordObject): Promise<GreetingRecord> {
-		return { greeting: 'Greetings, put!' };
-	}
-
-	async patch(target: RequestTargetOrId, record: Partial<GreetingRecord & RecordObject>): Promise<GreetingRecord> {
-		return { greeting: 'Greetings, patch!' };
-	}
-
-	async delete(target: RequestTargetOrId): Promise<boolean> {
-		return true;
-	}
-}

package/template-react-ts/schemas/examplePeople.graphql

@@ -1,7 +0,0 @@
-## Here we can define any tables in our database. This example shows how we define a type as a table using
-## the type name as the table name and specifying it is an "export" available in the REST and other external protocols.
-type ExamplePeople @table @export {
-	id: ID @primaryKey # Here we define primary key (must be one)
-	name: String # we can define any other attributes here
-	tag: String @indexed # we can specify any attributes that should be indexed
-}

package/template-vanilla/resources/examplePeople.js

@@ -1,14 +0,0 @@
-import { tables } from 'harperdb';
-
-export class ExamplePeople extends tables.ExamplePeople {
-	// we can define our own custom POST handler
-	post(content) {
-		// do something with the incoming content;
-		return super.post(content);
-	}
-	// or custom GET handler
-	get() {
-		// we can modify this resource before returning
-		return super.get();
-	}
-}

package/template-vanilla/resources/exampleSocket.js

@@ -1,34 +0,0 @@
-import { Resource, tables } from 'harperdb';
-
-export class ExampleSocket extends Resource {
-	static loadAsInstance = false;
-
-	// This customizes handling the socket connections; tables can have this method too!
-	async *connect(
-		target,
-		incomingMessages,
-	) {
-		const subscription = await tables.ExamplePeople.subscribe(target);
-		if (!incomingMessages) {
-			// Server sent events, no incoming messages!
-			// Subscribe to changes to the table.
-			return subscription;
-		}
-		for await (let message of incomingMessages) {
-			const { type, id, name, tag } = message;
-			switch (type) {
-				case 'get':
-					const loaded = await tables.ExamplePeople.get(id);
-					yield {
-						type: 'get',
-						id,
-						...(loaded ? loaded : {}),
-					};
-					break;
-				case 'put':
-					await tables.ExamplePeople.put(id, { name, tag });
-					break;
-			}
-		}
-	}
-}

package/template-vanilla/resources/greeting.js

@@ -1,10 +0,0 @@
-import { Resource } from 'harperdb';
-
-export class Greeting extends Resource {
-	// a "Hello, world!" handler
-	static loadAsInstance = false; // use the updated/newer Resource API
-
-	get() {
-		return { greeting: 'Hello, world!' };
-	}
-}

package/template-vanilla/schemas/examplePeople.graphql

@@ -1,7 +0,0 @@
-## Here we can define any tables in our database. This example shows how we define a type as a table using
-## the type name as the table name and specifying it is an "export" available in the REST and other external protocols.
-type ExamplePeople @table @export {
-	id: ID @primaryKey # Here we define primary key (must be one)
-	name: String # we can define any other attributes here
-	tag: String @indexed # we can specify any attributes that should be indexed
-}

package/template-vanilla-ts/resources/examplePeople.ts

@@ -1,20 +0,0 @@
-import { type RequestTargetOrId, tables } from 'harperdb';
-
-export interface ExamplePerson {
-	id: string;
-	name: string;
-	tag: string;
-}
-
-export class ExamplePeople extends tables.ExamplePeople<ExamplePerson> {
-	// we can define our own custom POST handler
-	async post(target: RequestTargetOrId, newRecord: Omit<ExamplePerson, 'id'>) {
-		// do something with the incoming content;
-		return super.post(target, newRecord);
-	}
-	// or custom GET handler
-	async get(target: RequestTargetOrId): Promise<ExamplePerson> {
-		// we can modify this resource before returning
-		return super.get(target);
-	}
-}

package/template-vanilla-ts/resources/exampleSocket.ts

@@ -1,41 +0,0 @@
-import { type IterableEventQueue, RequestTarget, Resource, tables } from 'harperdb';
-
-interface ExampleSocketRecord {
-	id: string;
-	type?: 'get' | 'put';
-	name: string;
-	tag: string;
-}
-
-export class ExampleSocket extends Resource<ExampleSocketRecord> {
-	static loadAsInstance = false;
-
-	// This customizes handling the socket connections; tables can have this method too!
-	async *connect(
-		target: RequestTarget,
-		incomingMessages: IterableEventQueue<ExampleSocketRecord>,
-	): AsyncIterable<ExampleSocketRecord> {
-		const subscription = await tables.ExamplePeople.subscribe(target);
-		if (!incomingMessages) {
-			// Server sent events, no incoming messages!
-			// Subscribe to changes to the table.
-			return subscription;
-		}
-		for await (let message of incomingMessages) {
-			const { type, id, name, tag } = message;
-			switch (type) {
-				case 'get':
-					const loaded = await tables.ExamplePeople.get(id);
-					yield {
-						type: 'get',
-						id,
-						...(loaded ? loaded : {}),
-					};
-					break;
-				case 'put':
-					await tables.ExamplePeople.put(id, { name, tag });
-					break;
-			}
-		}
-	}
-}

package/template-vanilla-ts/resources/greeting.ts

@@ -1,29 +0,0 @@
-import { type RecordObject, type RequestTargetOrId, Resource } from 'harperdb';
-
-interface GreetingRecord {
-	greeting: string;
-}
-
-export class Greeting extends Resource<GreetingRecord> {
-	static loadAsInstance = false;
-
-	async post(target: RequestTargetOrId, newRecord: Partial<GreetingRecord & RecordObject>): Promise<GreetingRecord> {
-		return { greeting: 'Greetings, post!' };
-	}
-
-	async get(target?: RequestTargetOrId): Promise<GreetingRecord> {
-		return { greeting: 'Greetings, get!' };
-	}
-
-	async put(target: RequestTargetOrId, record: GreetingRecord & RecordObject): Promise<GreetingRecord> {
-		return { greeting: 'Greetings, put!' };
-	}
-
-	async patch(target: RequestTargetOrId, record: Partial<GreetingRecord & RecordObject>): Promise<GreetingRecord> {
-		return { greeting: 'Greetings, patch!' };
-	}
-
-	async delete(target: RequestTargetOrId): Promise<boolean> {
-		return true;
-	}
-}

package/template-vanilla-ts/schemas/examplePeople.graphql

@@ -1,7 +0,0 @@
-## Here we can define any tables in our database. This example shows how we define a type as a table using
-## the type name as the table name and specifying it is an "export" available in the REST and other external protocols.
-type ExamplePeople @table @export {
-	id: ID @primaryKey # Here we define primary key (must be one)
-	name: String # we can define any other attributes here
-	tag: String @indexed # we can specify any attributes that should be indexed
-}