How readiz/boj works
Main Components
a. Problem Management Layer
• Problem Fetcher (get_problem.mjs)
• Problem Submitter (submit_problem.mjs)
• Problem Storage Structure (/boj directory)
b. Testing Layer
• C++ Test Runner (cpp_test.sh)
• Python Test Runner (py_test.sh)
• JavaScript Test Runner (js_test.sh)
c. Template System
• Language Templates (template.cpp, template.py, template.js, template.rs)
d. Problem Structure
• Problem Directory (contains desc.html, desc.md, input/, output/, solution/)
• Test Cases (input/ and output/ directories)
• Multiple Language Solutions
Component Relationships
• Command Line Interface → Problem Management Layer
• Problem Management Layer → Problem Structure
• Testing Layer → Problem Structure
• Template System → Problem Structure
Data Flow
Flows:
• User Input → Problem Fetcher → Problem Storage
• Problem Storage → Test Runners → Test Results
• Solution Files → Submit System → Online Judge
Special Elements
Features:
• External Dependencies (Chrome, Fonts, X Window)
• Build System Integration
• Test Case Management
• Multi-language Support
[User Interface Layer]
• ↓
[Problem Management Layer]
• ↓
[Language Support Layer]
• ↓
[Testing & Validation Layer]
• ↓
[Storage Layer]
Key Design Considerations:
Automation: Automated testing and submission processes
Technical details:
• WSL2 compatibility requirements
• External dependencies (Chrome, fonts, X Window)
• File system organization
• Testing infrastructure
The multi-language support system
This design captures both the technical architecture and the practical workflow of the BOJ problem-solving environment.