[#69] docs: create Plugin Design Guide #71
No reviewers
Labels
No labels
Compat/Breaking
Kind/Bug
Kind/Competitor
Kind/Documentation
Kind/Enhancement
Kind/Epic
Kind/Feature
Kind/Security
Kind/Story
Kind/Testing
Priority
Critical
Priority
High
Priority
Low
Priority
Medium
Reviewed
Confirmed
Reviewed
Duplicate
Reviewed
Invalid
Reviewed
Won't Fix
Scope/Core
Scope/Cross-Plugin
Scope/Plugin-System
Scope/Single-Plugin
Status
Abandoned
Status
Blocked
Status
Need More Info
No milestone
No project
No assignees
2 participants
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
ultanio/cobot!71
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "story-69"
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?
Closes #69
Summary
Creates
docs/plugin-design-guide.md— the authoritative reference for plugin design patterns and principles.Acceptance Criteria
docs/plugin-design-guide.mdContent Overview
capabilities,dependencies,consumes,implements, etc.)Referenced Files
All code examples point to real files with line numbers:
cobot/plugins/base.py(PluginMeta definition)cobot/plugins/knowledge/plugin.py(ToolProvider example)cobot/plugins/wallet/plugin.py(ToolProvider example)cobot/plugins/loop/plugin.py(consumes, extension_points examples)ups, in #73 Nazim also created a similiar PR. Can you compare and grab the best from #73 and add it here?
d465ee286bc55916f406