Val Town Code SearchReturn to Val Town

4import { DateTime } from "https://esm.sh/luxon@3.4.4";
5
6export async function testDailyBrief() {
7  try {
8    const testChatId = Deno.env.get("TEST_TELEGRAM_CHAT_ID");

2// Run this script manually to add new columns to the memories table
3
4export default async function migrateMemoriesDb() {
5  try {
6    // Import SQLite module

2// Run this script manually to create the database table
3
4export default async function setupTelegramChatDb() {
5  try {
6    // Import SQLite module

2// Run this script manually to set createdBy based on memory content
3
4export default async function populateCreatedBy() {
5  try {
6    // Import SQLite module

4import { nanoid } from "https://esm.sh/nanoid@5.0.5";
5
6export default async function populateMemoryIds() {
7  try {
8    // Import SQLite module

16In a normal server environment, you would likely use a middleware [like this one](https://hono.dev/docs/getting-started/nodejs#serve-static-files) to serve static files. Some frameworks or deployment platforms automatically make any content inside a `public/` folder public. 
17
18However in Val Town you need to handle this yourself, and it can be suprisingly difficult to read and serve files in a Val Town Project. This template uses helper functions from [stevekrouse/utils/serve-public](https://www.val.town/x/stevekrouse/utils/branch/main/code/serve-public/README.md), which handle reading project files in a way that will work across branches and forks, automatically transpiles typescript to javascript, and assigns content-types based on the file's extension.
19
20### `index.html`
26## CRUD API Routes
27
28This app has two CRUD API routes: for reading and inserting into the messages table. They both speak JSON, which is standard. They import their functions from `/backend/database/queries.ts`. These routes are called from the React app to refresh and update data.
29
30## Errors

6const tableName = "memories_demo";
7
8export async function getAllMemories(): Promise<Memory[]> {
9  const result = await sqlite.execute(
10    `SELECT id, date, text, createdBy, createdDate, tags FROM ${tableName}
23}
24
25export async function createMemory(
26  memory: Omit<Memory, "id">
27): Promise<Memory> {
51}
52
53export async function updateMemory(
54  id: string,
55  memory: Partial<Omit<Memory, "id">>
70}
71
72export async function deleteMemory(id: string): Promise<void> {
73  await sqlite.execute(`DELETE FROM ${tableName} WHERE id = ?`, [id]);
74}

4
5* `migrations.ts` - code to set up the database tables the app needs
6* `queries.ts` - functions to run queries against those tables, which are imported and used in the main Hono server in `/backend/index.ts`
7
8## Migrations
18The queries file is where running the migrations happen in this app. It'd also be reasonable for that to happen in index.ts, or as is said above, for that line to be commented out, and only run when actual changes are made to your database schema.
19
20The queries file exports functions to get and write data. It relies on shared types and data imported from the `/shared` directory.

54}
55
56export function NotebookView({ onClose, avatarUrl }: NotebookViewProps) {
57  const [memories, setMemories] = useState<Memory[]>([]);
58  const [loading, setLoading] = useState(true);

62};
63
64export function App() {
65  const [memories, setMemories] = useState<Memory[]>([]);
66  const [loading, setLoading] = useState(true);
139      const data = await response.json();
140
141      // Change the sorting function to show memories in chronological order
142      const sortedMemories = [...data].sort((a, b) => {
143        const dateA = a.createdDate || 0;