Add basic shape tools to the example drawing area
Los mantenedores suelen responder en 1 día
@Chuyutseng ya está trabajando en esto.
Desde el 8/11/2026.
Evaluación
Este issue todavía no se ha evaluado.
Descripción
Observed behavior
The Example drawing area introduced in PR #262 allows candidates to illustrate examples during coding interviews without hiding the code editor. It currently supports freehand drawing, erasing, undo, clear, color selection, and text labels, but does not provide tools for drawing basic geometric shapes.
Candidates must manually draw rectangles, circles, and straight lines using the pen tool, making it difficult to create consistent diagrams when explaining data structures, algorithms, or relationships between elements.
Expected behavior
The Example drawing area should support three additional drawing tools:
- Rectangle: Draw a rectangle between two points.
- Ellipse: Draw a circle or ellipse within the dragged bounds.
- Line: Draw a straight line between two points.
Candidates should be able to preview a shape while dragging and complete it when releasing the pointer.
Each completed shape should behave as a single undoable operation, reuse the existing color selection, and remain compatible with recording, replay, and reconnection.
Reproduction
- Start a Coding interview with Example drawing enabled.
- Expand the Example drawing area below the code editor.
- Observe that the toolbar provides pen, eraser, text, undo, clear, and color selection.
- Attempt to draw a rectangle, circle, or straight line.
- Observe that these shapes must be drawn manually using the pen tool.
Initial analysis
The drawing model and rendering logic are implemented in web/whiteboard.js, with corresponding tests in tests/browser/whiteboard.test.js. The existing drawing operations support undo, clearing, and replay through a shared drawing model.
PR #523 introduced structured text operations shared by Whiteboard and Example drawing. The proposed shape tools should reuse the existing drawing infrastructure where possible.
The implementation would need to consider:
- Toolbar controls: Add rectangle, ellipse, and line tools alongside the existing drawing controls.
- Pointer handling: Track the initial pointer position and current position to determine shape geometry.
- Drawing preview: Render temporary shapes during dragging without adding intermediate previews to the operation history.
- Operation history: Commit each completed shape as a single undoable operation.
- Recording and replay: Ensure that completed shapes are preserved and rendered correctly.
- Reconnection: Retain completed drawings after reconnecting.
The operation representation should minimize changes to the existing drawing protocol while preserving compatibility with recording, replay, and reconnection.
Proposed change
Extend the Example drawing area with three basic shape tools: Rectangle, Ellipse, and Line.
Selecting a shape tool should allow candidates to press, drag, and release the pointer to create the corresponding shape. A temporary preview should be displayed during dragging, and the completed shape should be committed to the drawing history when the pointer is released.
The implementation should preserve existing pen, eraser, text, undo, clear, color selection, recording, replay, and reconnection behavior.
Validation plan
Add browser regression tests covering:
- Rectangle, ellipse, and line creation using pointer interactions.
- Shape geometry when dragging in different directions.
- Shape preview and final rendering.
- Color selection for newly created shapes.
- Undo and clear behavior for completed shapes.
- Recording and replay of drawings containing geometric shapes.
- Preservation of completed shapes after reconnection.
- Regression coverage for existing pen, eraser, and text tools.
Tests should verify the actual drawing output rather than only checking whether toolbar buttons or canvas elements are visible.
Run ./scripts/test.sh and report the results, including any skipped checks.
- Lenguaje dominante
- Rust
- Estrellas
- 223
- Forks
- 148
- Merge medio
- 1 d 4 h
- PR fusionados (30 d)
- 223
Preparar el entorno
- Sin Dockerfile ni archivo de Docker Compose
- Tiene una plantilla de pull request
- Leer la guía de contribución
Primeros pasos
- Lee el issue completo y luego la guía de contribución del proyecto.
- Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
- Haz un fork del repositorio y trabaja en una rama.
- Abre un pull request que haga referencia al número del issue.
Más de sysprog21/codetrial
-
Dificultad 1/5 Menos de una hora Aptitud para principiantes 84/100
Los mantenedores suelen responder en 1 día
-
Show recorded scores in past attempt rowsPosiblemente ocupada @liehcheng la tomó hace 1 día. Abierto
Dificultad 2/5 1-3 horas Aptitud para principiantes 78/100
sysprog21/codetrial#604 · 4 comentarios · 1 asignado ·
Los mantenedores suelen responder en 1 día
-
Remind the candidate when they speak while the microphone is mutedPosiblemente ocupada @gino1203 la tomó hoy. Abierto
sysprog21/codetrial#627 · 1 asignado ·
Los mantenedores suelen responder en 1 día
-
The peer lobby stays on "Checking account..." when an invite link is opened with site data blockedPosiblemente ocupada @dges5202 la tomó hoy. Abierto
sysprog21/codetrial#626 · 3 comentarios · 1 asignado ·
Los mantenedores suelen responder en 1 día
-
Browser-local practice backendPosiblemente ocupada @tony2037 la tomó hoy. Abierto
sysprog21/codetrial#621 · 2 comentarios · 1 asignado ·
Los mantenedores suelen responder en 1 día
Todos los issues de sysprog21/codetrial
Issues similares
-
needs-triage tooling
Dificultad 1/5 Menos de una hora Aptitud para principiantes 90/100
neilsh/stunt-reel#317 ·
Los mantenedores suelen responder en 1 día
-
Dificultad 2/5 1-3 horas Aptitud para principiantes 84/100
storytold/craft-fonts#65 ·
Los mantenedores suelen responder en 2 días
-
Dificultad 2/5 1-3 horas Aptitud para principiantes 86/100
storytold/craft-libs#723 ·
Los mantenedores suelen responder en 1 día
-
Dificultad 2/5 1-3 horas Aptitud para principiantes 83/100
n0-computer/iroh#4669 · 1 comentario ·
Los mantenedores suelen responder en 1 día
-
Dificultad 2/5 1-3 horas Aptitud para principiantes 78/100
jdx/mise#15471 · 1 comentario ·
Los mantenedores suelen responder en 1 día