Track WP26 CubeSat and stakeholder-chain editor feedback

Đang mở
#35 0 bình luận 0 reaction 0 người được giao Xem trên GitHub

Maintainer thường phản hồi trong vòng 1 ngày

Chưa có ai nhận issue này.

Đánh giá

Độ khó
2/5
Thời gian dự kiến
1-3 giờ
Mức phù hợp với người mới
15/100
Loại issue
Tài liệu
Độ rõ ràng
Đặc tả rõ ràng
Mức độ hoạt động
Sôi nổi
Công nghệ
react, typescript

Hướng nghiên cứu

Read the linked WP26 feedback report and its screenshots, then follow the referenced editor issues and implementation updates. Compare reported findings with the exact current build and engine pins, keeping reproduced defects distinct from unverified expectations. Done when each item’s status and evidence are accurately tracked without implying unverified fixes, deployment, or conformance decisions.

Do mô hình lập chỉ mục viết ra từ nội dung của issue.

Mô tả

Track Zargham’s 2026-11-10 CubeSat/stakeholder-model feedback against the view editor. This is intake, not evidence that maintainers have reproduced or accepted every reported expectation.

Report pinned to the reported revision · 31 screenshots · Model sources.

Reported bugs and missing capabilities

Stakeholder-to-evidence chain

F-5 is combined with Bug 4 above because they require the same case-rendering capability.

Other actionable suggestions and reading workflows

Evidence and scope rules

  • Bug 1 did not reproduce in the report’s cold pass. Bug 2 may reflect the last successful save, and later instances followed a competing-tab save failure; silent loss has not been established.
  • Bugs 8–9 are parser disagreements requiring authoritative semantic analysis. Another parser accepting source does not establish correctness.
  • Bug 6 compares different filters/projections; verify exposure, filter and representation semantics independently before treating the difference as a defect.
  • The app already supports multi-file import. Bug 3 requests adding files to an existing open project.
  • The dated hosted build was not identified by commit. Compare each finding with an exact current build and engine pins before claiming a fix or deployment.
  • The report’s screenshot-lag observation (section 2 item 11) has no established editor cause. Qualify whether it belongs to the browser/automation capture surface before filing a product defect. External tab navigation/interference was explicitly excluded by the report.
  • Preserve the successes: named views, source/issue inspection, requirements and negated satisfaction, CSV/matrix workflows, and the distinction between declared verification and executed results.
  • No delivery dates, assignments, conformance decisions, local reproductions or deployed fixes are implied by this intake. The editor guide merged in PR #13 addresses discoverability, not proof that the reported usability concerns are resolved.

Issues were requested in this repository only; no GitHub Project board was created or populated.

Implementation update — 2026-11-11

  • #14 and #18 are implemented and locally verified; PR #37 into develop is pending hosted checks at head 618e776. Issues were closed at the requester’s direction; merge/deployment are not claimed. The synchronization commit has the same file tree as tested 3ca0d7f. Verification and limits.
  • #15 and #23 are closed after PR #36 merged into develop as 2f58240 on 2026-11-11. Deployment is not established.
  • #20 remains open: immediate exposure can legitimately include private imported memberships, while a separate intermediate-import admission defect is reproduced. Investigation and retained upstream reproduction. No safe resolver fix is integrated.
  • The other items remain open. No claim that all WP26 feedback is resolved or that a hosted deployment changed.
Ngôn ngữ chính
TypeScript
Star
2
Fork
0
Merge trung bình
15 giờ 5 phút
Pull request đã merge (30 ngày)
15

Chuẩn bị môi trường

Bắt đầu từ đâu

  1. Đọc hết issue, rồi đọc hướng dẫn đóng góp của dự án.
  2. Bình luận trên issue rằng bạn sẽ nhận — tránh hai người làm cùng một việc.
  3. Fork repository và làm thay đổi trên một nhánh.
  4. Mở pull request có tham chiếu số hiệu của issue.

Issue khác của Open-MBEE/sysml_view_editor

Tất cả issue của Open-MBEE/sysml_view_editor

Issue tương tự

Thêm issue về TypeScript

Nhận issue mới trong hộp thư của bạn

Bản tóm tắt ngắn những issue GitHub phù hợp với người mới.