Make table and model-tree selection reveal useful, predictable details

オープン
#33 コメント 0 件 リアクション 0 件 担当者 0 名 GitHub で見る

メンテナーはふだん 1 日以内に返信

まだ誰も着手していません。

評価

難易度
5/5
見積もり時間
1週間以上
初心者へのやさしさ
35/100
issue の種類
機能追加
明瞭さ
おおむね明確
活発さ
活発
技術スタック
react, typescript

調査の方向性

Start with the Requirements table and model-tree selection handlers, Inspector visibility and navigation to named views; the payload does not identify their file paths or tests. First reproduce the reported workflow in the hosted editor, then record the engine/build identity and check current behavior against the report. Done means selection, source navigation, hidden Inspector, pending feedback and missing targets have defined behavior, with pointer and keyboard paths covered and drafts and the last valid model preserved.

索引モデルが issue の本文から書いたものです。

説明

enhancement

Source and status

WP26 feedback report — Suggestion 11; section 2 items 14–16. 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 observations from a cold reader; detailed interaction traces were not retained. Exact causes remain unverified.

Problem

A requirements-row click navigated to source after a delay rather than opening the expected details; tree selection could appear to do nothing when Inspector was hidden. A reader also failed to reach a requested metrics view.

Reproduction / requested workflow

  1. Open Requirements table and select a requirement.
  2. Select a model-tree element with Inspector collapsed.
  3. Navigate to another named view and observe readiness and selection feedback.

Acceptance / investigation criteria

  • Define clear selection-versus-source-navigation behavior for read-only inspection.
  • Make selected details and hidden Inspector discoverable without losing drafts or surprising panel changes.
  • Show pending navigation/inspection feedback and confirm the requested view is active.
  • Cover pointer/keyboard behavior and missing source targets.

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.

主要言語
TypeScript
スター
2
フォーク
0
平均マージ
13時間 40分
マージ済み PR(30日)
17

環境構築

はじめの一歩

  1. issue を最後まで読み、次にプロジェクトのコントリビューションガイドを読みます。
  2. 着手することを issue にコメントします — 二人が同じ作業をするのを防げます。
  3. リポジトリをフォークし、ブランチを切って変更します。
  4. issue 番号を参照したプルリクエストを送ります。

Open-MBEE/sysml_view_editor のほかの issue

Open-MBEE/sysml_view_editor の issue をすべて見る

似ている issue

TypeScript の issue をもっと見る

新しい issue をメールで受け取る

初心者向けの GitHub issue を短くまとめたダイジェスト。