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

CLI Architecture Technical Debt: Consolidate Command Implementations #157

New Issue
Open
opened 2025-10-14 17:45:20 +00:00 by tegwick · 0 comments
tegwick commented 2025-10-14 17:45:20 +00:00
Owner
Copy Link

The MarkiTect codebase has accumulated significant CLI architecture technical debt with multiple conflicting command implementations, inconsistent patterns, and architectural fragmentation.

Problems

  • Multiple conflicting CLI implementations (markitect/cli.py vs markitect/cli/ directory)
  • Import conflicts breaking existing CLI imports
  • Inconsistent command patterns across modules
  • Click testing framework I/O conflicts
  • Fragmented test structures

Proposed Solution

Consolidate to single canonical CLI architecture with:

  • markitect/cli.py as main entry point
  • markitect/cli/ directory for organized command modules
  • Consistent command group structure using @click.group()
  • Standardized error handling and output formatting
  • Unified testing patterns

Benefits

  • Single canonical architecture
  • Consistent patterns for maintainability
  • Better user experience with predictable commands
  • Simplified testing and debugging

See detailed analysis in .markitect_workspace/cli_architecture_technical_debt.md

Priority: High (Technical Debt)
Estimated Effort: 1-2 weeks

The MarkiTect codebase has accumulated significant CLI architecture technical debt with multiple conflicting command implementations, inconsistent patterns, and architectural fragmentation. ## Problems - Multiple conflicting CLI implementations (markitect/cli.py vs markitect/cli/ directory) - Import conflicts breaking existing CLI imports - Inconsistent command patterns across modules - Click testing framework I/O conflicts - Fragmented test structures ## Proposed Solution Consolidate to single canonical CLI architecture with: - markitect/cli.py as main entry point - markitect/cli/ directory for organized command modules - Consistent command group structure using @click.group() - Standardized error handling and output formatting - Unified testing patterns ## Benefits - Single canonical architecture - Consistent patterns for maintainability - Better user experience with predictable commands - Simplified testing and debugging See detailed analysis in .markitect_workspace/cli_architecture_technical_debt.md Priority: High (Technical Debt) Estimated Effort: 1-2 weeks
tegwick added this to the Improvements project 2025-10-14 22:21:25 +00:00
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 Improvements
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#157
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?