-
-
Notifications
You must be signed in to change notification settings - Fork 241
Migrate core event system from EventEmitter3 to Eventa #567
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Open
luoling8192
wants to merge
4
commits into
main
Choose a base branch
from
claude/refactor-event-system-Nv6Uc
base: main
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
Open
Changes from all commits
Commits
Show all changes
4 commits
Select commit
Hold shift + click to select a range
013a870
refactor(core): migrate event system to @moeru/eventa (Phases 1-3)
claude c4386ea
refactor(core, server, bot, client): complete Eventa migration Phase 4
claude c4ae8a7
refactor: catalog
luoling8192 d2a5cb5
[autofix.ci] apply automated fixes
autofix-ci[bot] File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -0,0 +1,45 @@ | ||
| /** | ||
| * Server-side event dispatch for bridging JSON-over-WebSocket messages to Eventa events. | ||
| * | ||
| * Uses shared event maps from @tg-search/core and adds server-specific | ||
| * dispatch logic (invoking RPCs and sending responses back to the calling peer). | ||
| */ | ||
| import type { CoreContext } from '@tg-search/core' | ||
| import type { Peer } from 'crossws' | ||
|
|
||
| import { defineInvoke } from '@moeru/eventa' | ||
| import { fireAndForgetEvents, isCoreEvent, rpcEvents } from '@tg-search/core' | ||
|
|
||
| import { sendWsEvent } from './events' | ||
|
|
||
| export { isCoreEvent } | ||
|
|
||
| /** | ||
| * Dispatch an incoming client event to the core Eventa context. | ||
| * | ||
| * - Fire-and-forget events are emitted directly. | ||
| * - RPC invokes are awaited and their response is sent back to the calling peer. | ||
| */ | ||
| export async function dispatchClientEvent( | ||
| ctx: CoreContext, | ||
| eventName: string, | ||
| data: any, | ||
| peer: Peer, | ||
| ): Promise<void> { | ||
| // Try RPC invoke first | ||
| const rpc = rpcEvents.get(eventName) | ||
| if (rpc) { | ||
| const invoke = defineInvoke(ctx.ctx, rpc.invoke) | ||
| const result = await invoke(data) | ||
| sendWsEvent(peer, rpc.responseEvent, result) | ||
| return | ||
| } | ||
|
|
||
| // Try fire-and-forget | ||
| const event = fireAndForgetEvents.get(eventName) | ||
| if (event) { | ||
| ctx.ctx.emit(event, data) | ||
| } | ||
|
|
||
| // Unknown event — skip silently (may be server-only) | ||
| } |
Oops, something went wrong.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The new server-side static
notificationEventslist omitsmessage:processed, even though this commit still defines it as a core notification in the shared dispatch map. In WebSocket/server mode, clients that register formessage:processedwill no longer receive batch completion events, creating a behavior regression and inconsistency versus core-bridge mode where this notification is still wired.Useful? React with 👍 / 👎.