coulomb/markitect-main
2
0
Fork 0
Code Issues 60 Pull Requests Actions 1 Projects 12 Releases 1 Wiki Activity

Capture actual heading text in schemas #52

New Issue
Closed
opened 2025-10-01 00:02:22 +00:00 by tegwick · 0 comments
tegwick commented 2025-10-01 00:02:22 +00:00
Owner
Copy Link

UseCase: As a user creating schemas from documents, I want the schema to preserve the actual heading text from the source document, so that generated drafts maintain consistent section titles and structure.

Technical Requirements:
Modify schema generation to store actual heading text alongside structural information, enabling schemas to specify required heading text that must appear in documents validated against the schema.

Acceptance Criteria:

  • Schema captures exact heading text from source document
  • Schema validation can enforce specific heading text requirements
  • Heading text is preserved in outline structure representation
  • Generated schemas include heading text as schema constraints
  • Backward compatibility with existing schemas maintained
  • Schema validation provides meaningful errors for heading text mismatches

Dependencies:

  • Current schema generation system (Issue #5)
  • Schema validation system (Issue #7)
  • Metaschema definition (Issue #50)
UseCase: As a user creating schemas from documents, I want the schema to preserve the actual heading text from the source document, so that generated drafts maintain consistent section titles and structure. Technical Requirements: Modify schema generation to store actual heading text alongside structural information, enabling schemas to specify required heading text that must appear in documents validated against the schema. Acceptance Criteria: - [ ] Schema captures exact heading text from source document - [ ] Schema validation can enforce specific heading text requirements - [ ] Heading text is preserved in outline structure representation - [ ] Generated schemas include heading text as schema constraints - [ ] Backward compatibility with existing schemas maintained - [ ] Schema validation provides meaningful errors for heading text mismatches Dependencies: - Current schema generation system (Issue #5) - Schema validation system (Issue #7) - Metaschema definition (Issue #50)
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
priority:critical
Critical priority issue
 priority:high
High priority issue
 priority:low
Low priority issue
 priority:medium
Medium priority issue
 status:active
Issues currently being worked on
 status:blocked
Issues blocked by dependencies
 status:done
Completed issues
 status:review
Issues under review
 status:todo
Issues ready to be worked on
 type:bug
Bug report
 type:documentation
Documentation update
 type:enhancement
Enhancement to existing feature
 type:feature
New feature request
 wish
Feature wishlist item - idea to be discussed and refined
 wish/archived
Archived or rejected wishlist item
 wish/discussion
Wishlist item currently being discussed and refined
 wish/draft
Wishlist item with initial draft specification
 wish/ready
Wishlist item ready to become a regular issue
No Label
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
bubble-reader tegwick
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: coulomb/markitect-main#52
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?