Story: Fix telegram plugin call_extension API mismatch #104
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
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
ultanio/cobot#104
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
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?
Epic: #101
Description
The telegram plugin's
_call_extensionmethod (line 582) callsself._registry.call_extension(point, ctx), butPluginRegistryno longer has acall_extensionmethod. This was moved toBasePlugin.call_extension()(async, line 125 of base.py).This causes an
AttributeErrorcrash in the telegram poll loop at runtime.Root Cause
API refactoring moved
call_extensionfromPluginRegistrytoBasePluginbut the telegram plugin was not updated.Fix Options
_call_extensionasync, useawait self.call_extension(point, ctx)from BasePlugin, propagate async to callersself._registry.call_extension()call since the local handler loop already worksRecommend option 1 for long-term alignment.
Acceptance Criteria
_call_extensionusesBasePlugin.call_extension()(not registry directly)AttributeErrorruff check cobot/passes