jaraco / jaraco/irc

Implement default handler if nothing matches

Open
#185 1 comment 0 reactions 0 assignees View on GitHub
enhancement help wanted
Dominant language
Python
Stars
421
Forks
90
PR merge metrics
No merged PRs in 30d

Description

There's an undocumented(?) event handler named `all_events` but I'd also like to have a catch-all for unhandled events called `unhandled_event` or something so handlers can be registered at reactor level directly where they exist and others fall through to a catch-all.

I'm now at a point I either need to refactor my project completely to use a custom event handler based on `all_events` or get an upstream solution as there's too many non-standard reply codes to catch all of them manually.

Would this be doable?

Thanks.

Contributor guide

No contributing guide indexed for this repository

Research direction

Start by reading the existing `all_events` handler and the reactor-level event registration path. Clarify the intended name and dispatch behavior for a catch-all handler, including how unhandled events and non-standard reply codes are identified. Done should include an agreed upstream API and coverage for the fallback behavior.

Written by the indexing model from the issue text.

Assessment

Tech stack
python
Domain
backend
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.