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

Prefix markdown commands with md- prefix #44

New Issue
Closed
opened 2025-09-30 21:07:26 +00:00 by tegwick · 0 comments
tegwick commented 2025-09-30 21:07:26 +00:00
Owner
Copy Link

For consistency we should have prefixes for get, ingest, list.

Well I am not sure. Let's think about that from a plugin framework perspectiv.
Can the Markdown capability we started from be a plugin, too? Does it make sense to separate it into a plugin?
If so the command prefix should definitely reflect the idea that each plugin provides a cli prefix as something like a subcommand namespace. That helps to understand and structure the system.

Provide an architectural swat analysis and enable me to make an informed decision.

My guess is going full plugin style could provide elegance and maintainability. I thought about going with a lazyload model for the plugins and it might be strange to have different architecture paradigms in parallel.

For consistency we should have prefixes for get, ingest, list. Well I am not sure. Let's think about that from a plugin framework perspectiv. Can the Markdown capability we started from be a plugin, too? Does it make sense to separate it into a plugin? If so the command prefix should definitely reflect the idea that each plugin provides a cli prefix as something like a subcommand namespace. That helps to understand and structure the system. Provide an architectural swat analysis and enable me to make an informed decision. My guess is going full plugin style could provide elegance and maintainability. I thought about going with a lazyload model for the plugins and it might be strange to have different architecture paradigms in parallel.
tegwick added this to the Usability project 2025-09-30 21:07:26 +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 Usability
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#44
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?