Clarify Code, Split and Diagram layout controls for first-time readers

Abierto
#32 0 comentarios 0 reacciones 0 asignados Ver en GitHub

Los mantenedores suelen responder en 1 día

Nadie ha tomado este issue todavía.

Evaluación

Dificultad
4/5
Tiempo estimado
3-5 días
Aptitud para principiantes
55/100
Tipo de issue
Nueva funcionalidad
Claridad
Bastante claro
Estado de actividad
Activo
Stack tecnológico
react, typescript

Línea de trabajo

Start by locating the toolbar controls for Code, Split and Diagram, then trace how they set the editor layout and how startup defaults interact with user preferences. Reproduce the reported workflow with pointer and keyboard input, recording the exact engine and build identity. Done when each mode’s effect is clear before selection, the active mode is apparent, Split is easy to find, and unapplied drafts and the last valid model are preserved.

Escrito por el modelo de indexación a partir del texto del issue.

Descripción

enhancement

Source and status

WP26 feedback report — Suggestion 11; section 2 item 12. Session dated 2026-11-10, using the hosted editor as served that day; deployed commit was not identified. The report does not establish current develop or current deployment behavior.

Reported usability observation from a cold reader; no screenshot or independent local reproduction retained.

Problem

A read-only reviewer expected a layout toggle and was surprised when the first click replaced the diagram with source. The guide may help discovery but is not evidence this workflow is resolved.

Reproduction / requested workflow

  1. Open a project as a first-time reader.
  2. Identify the toolbar layout buttons without consulting source code.
  3. Switch Code, Split and Diagram using pointer and keyboard.

Acceptance / investigation criteria

  • Make each mode’s consequence discoverable before activation.
  • Indicate the active mode clearly and make Split easy to discover.
  • Evaluate startup defaults without blindly overriding user preferences or changing project data.

Evidence

Model files at the reported revision.

Preserve unapplied drafts and the last valid model. Record exact engine/build identity and distinguish a reported observation from a newly reproduced result.

Lenguaje dominante
TypeScript
Estrellas
2
Forks
0
Merge medio
13 h 40 min
PR fusionados (30 d)
17

Preparar el entorno

Primeros pasos

  1. Lee el issue completo y luego la guía de contribución del proyecto.
  2. Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
  3. Haz un fork del repositorio y trabaja en una rama.
  4. Abre un pull request que haga referencia al número del issue.

Más de Open-MBEE/sysml_view_editor

Todos los issues de Open-MBEE/sysml_view_editor

Issues similares

Más issues de TypeScript

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.