Distinguish rendering and inspection activity from unapplied source drafts

Aperta
#34 0 commenti 0 reazioni 0 assegnatari Vedi su GitHub

I maintainer di solito rispondono entro 1 giorno

Nessuno ha ancora preso questa issue.

Valutazione

Difficoltà
5/5
Tempo stimato
Più di una settimana
Idoneità per principianti
25/100
Tipo di issue
Bug
Chiarezza
Abbastanza chiara
Stato di attività
Attiva
Stack tecnologico
react, typescript

Direzione di ricerca

Start with Suggestion 11 in the linked WP26 feedback report and compare its reported observation with the current editor behavior; the issue says the deployed commit was not identified and the behavior has not been reproduced locally. Trace how toolbar/header status and Apply availability reflect source equality, engine work, failures, and recovery. Done means reproducing with exact operation and build identity and verifying that progress is distinct from unapplied drafts while preserving drafts and the last valid model.

Scritto dal modello di indicizzazione a partire dal testo della issue.

Descrizione

bug

Source and status

WP26 feedback report — Suggestion 11; section 2 item 17. 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 transient behavior; no dedicated cold-reader screenshot retained. Not locally reproduced.

Problem

A reader who made no edit reportedly saw “Applied revision · draft pending”, “Working…” and an enabled Apply source transiently during browsing/restores. That wording made them think the source had changed.

Reproduction / requested workflow

  1. Restore or apply a project, then browse views and inspection surfaces without editing source.
  2. Observe toolbar/header state during engine work.
  3. Compare actual draft/applied source equality and transaction history.

Acceptance / investigation criteria

  • Reproduce with exact operation/build identity; do not equate all busy state with source changes.
  • Show rendering/inspection progress separately from genuine unapplied drafts.
  • Enable Apply only under the intended source-state rules.
  • Retain correct status during real edits, failures and recovery.

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.

Lingua principale
TypeScript
Stelle
2
Fork
0
Merge medio
15h 5m
PR unite (30g)
15

Preparare l'ambiente

Come iniziare

  1. Leggi tutta la issue e poi la guida ai contributi del progetto.
  2. Commenta sulla issue per dire che te ne occupi tu — evita che due persone facciano lo stesso lavoro.
  3. Fai un fork del repository e lavora su un branch.
  4. Apri una pull request che faccia riferimento al numero della issue.

Altre issue di Open-MBEE/sysml_view_editor

Tutte le issue di Open-MBEE/sysml_view_editor

Issue simili

Altre issue su TypeScript

Ricevi le nuove issue nella tua casella

Un breve riepilogo di issue GitHub adatte ai principianti.