Rbanh/schemeta
1
0
Fork 0
Code Issues 11 Pull Requests Actions 1 Packages Projects Releases Wiki Activity

P5-04: JSON schema import UX pass (validation-first flow) #27

New Issue
Closed
opened 2026-02-19 13:41:35 -05:00 by Rbanh · 1 comment
Rbanh commented 2026-02-19 13:41:35 -05:00
Owner
Copy Link

Objective

Make JSON import/apply predictable, safe, and understandable for large AI-generated payloads.

Scope

  • Inline schema validation summary before apply.
  • Highlight parse/schema errors with actionable locations.
  • Improve import feedback messaging for changed instances/nets/symbols.

Acceptance Criteria

  • Invalid JSON/schema errors are clearly surfaced before apply.
  • Valid imports show deterministic change summary and compile outcome.
  • Import flow supports large schema-conformant circuits without ambiguous state.
## Objective Make JSON import/apply predictable, safe, and understandable for large AI-generated payloads. ## Scope - Inline schema validation summary before apply. - Highlight parse/schema errors with actionable locations. - Improve import feedback messaging for changed instances/nets/symbols. ## Acceptance Criteria - Invalid JSON/schema errors are clearly surfaced before apply. - Valid imports show deterministic change summary and compile outcome. - Import flow supports large schema-conformant circuits without ambiguous state.
Rbanh added this to the Phase 5 - Layout Robustness and JSON Import UX Hardening milestone 2026-02-19 13:42:00 -05:00
Rbanh commented 2026-02-19 14:00:41 -05:00
Author
Owner
Copy Link

Delivered in commit 8b6c959.

What shipped:

  • Added validation-first apply/import flow in frontend/app.js (analyzeModelForImport).
  • Apply JSON and file import now run /analyze before compile.
  • Apply/import is blocked on validation errors with actionable message + first issue path.
  • Successful apply/import now includes deterministic change summary + warning count feedback.

Verification:

  • UI regression now asserts invalid apply is blocked and does not mutate compiled state.
Delivered in commit `8b6c959`. What shipped: - Added validation-first apply/import flow in `frontend/app.js` (`analyzeModelForImport`). - `Apply JSON` and file import now run `/analyze` before compile. - Apply/import is blocked on validation errors with actionable message + first issue path. - Successful apply/import now includes deterministic change summary + warning count feedback. Verification: - UI regression now asserts invalid apply is blocked and does not mutate compiled state.
Rbanh closed this issue 2026-02-19 14:00:52 -05:00
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
No items
No Label
Milestone
Clear milestone
No items
No Milestone
Phase 5 - Layout Robustness and JSON Import UX Hardening
Projects
Clear projects
No project
Assignees
Clear assignees
No Assignees
1 Participants
Notifications
Due Date
The due date is invalid or out of range. Please use the format 'yyyy-mm-dd'.

No due date set.

Dependencies

No dependencies set.

Reference: Rbanh/schemeta#27
No description provided.
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?