TraceOJ

TraceOJ is a local-first OJ knowledge base for organizing solutions, notes, relations, and review plans.

It focuses on long-term practice workflow instead of one-time note dumping.

✨ Overview

• Multi-platform import from local folders
• Filename-driven metadata parsing and normalization
• Problem tagging, status tracking, and review flags
• Relation modeling for similar/equivalent/path links
• Dedicated review queue with review logs
• Dashboard snapshots for practice history

🚀 Core Features

📚 Problem Management

• Store platform, IDs, title, source file path, rendered content, notes, tags, status, review fields, and timestamps
• View and edit metadata from problem detail pages
• Keep all records in a normalized relational schema

⚙️ Import Pipeline

• Recursive directory scanning
• Platform auto-detection
• Filename parsing rules per platform
• Incremental upsert by platform + originalId
• Import logs with success/update/skip/failure counts

🔗 Relation Parsing

Current LeetCode filename rules support:

• - for learning path / sequence
• ~ for similar problems
• == for equivalent problems
• multiple parentheses in one filename
• non-numeric IDs such as LCR131

📝 Review Workflow

• Mark any problem into review queue
• Record review actions through review logs
• Keep extensible fields for future spaced-repetition strategies

🧱 Tech Stack

• Next.js 16 App Router
• TypeScript
• Tailwind CSS
• Prisma
• SQLite
• React Markdown + highlight.js
• Vitest

🌍 Supported Platforms

• LeetCode
• Luogu
• ...

Parser architecture is extensible and ready for additional platforms.

🗂️ Project Structure

TraceOJ
├─ app
│  ├─ dashboard
│  ├─ import
│  ├─ login
│  ├─ problems
│  │  └─ [id]
│  ├─ review
│  ├─ sequences
│  ├─ globals.css
│  ├─ icon.svg
│  ├─ layout.tsx
│  └─ page.tsx
├─ components
├─ examples
│  └─ import-demo
├─ lib
│  ├─ actions
│  ├─ data
│  └─ parsers
├─ prisma
│  ├─ init.sql
│  ├─ schema.prisma
│  └─ seed.ts
├─ scripts
│  └─ import-problems.ts
├─ tests
│  └─ leetcode-parser.test.ts
├─ .env.example
├─ package.json
└─ README.md

🛢️ Database Model

Main tables:

• Problem
• Tag
• ProblemTag
• ProblemRelation
• SequenceGroup
• SequenceItem
• ImportLog
• ReviewLog

Important design decisions:

• Problem.originalId is a string, not an integer
• Placeholder problems can be created for unresolved references
• Relation types include similar, equivalent, and manual
• Sequence data is stored separately from pairwise relations

🛠️ Quick Start

1. 📦 Install dependencies

npm install

2. 🔐 Create environment file

Create .env from .env.example.

Example:

DATABASE_URL="file:./dev.db"
AUTH_SECRET="change-this-secret"
ADMIN_PASSWORD="your-password"

3. 🧬 Initialize database

npm run db:generate
npm run db:init

4. 🌱 Seed example data

npm run db:seed

5. ▶️ Start development server

npm run dev

Then open:

• http://localhost:3000

📥 Import Local Notes

Import from your local problem directory:

npm run import-problems -- "D:/oj-notes"

Use the sample directory:

npm run import-problems -- "examples/import-demo"

💻 Development Commands

npm run dev
npm run import-problems -- "examples/import-demo"

✅ Test And Build

npm run test
npm run lint
npm run build

🧭 Roadmap

• More platform parsers
• Better review scheduling
• Richer relation graph views
• Full-text search
• Bulk editing for status and tags
• Export to Markdown / JSON

🤝 Contributing

Issues and pull requests are welcome. For larger changes, open an issue first to discuss scope and design.