[#104] Fix telegram plugin call_extension API mismatch #111
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!111
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "story-104"
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 #104
Problem
The telegram plugin's
_call_extension()method calledself._registry.call_extension(point, ctx)which no longer exists onPluginRegistry. This method was moved toBasePlugin.call_extension()(async) during a refactor, but the telegram plugin was not updated.This caused an
AttributeErrorcrash in the telegram poll loop at runtime.Fix
Removed the broken
self._registry.call_extension()call. The local extension handler loop already works correctly for registered handlers. Cross-plugin async dispatch viaBasePlugin.call_extension()can be added in a future PR if needed.Acceptance Criteria
ruff check cobot/passesf9c29ab86b80a8128db4