Skip to content

Conversation

Copy link

Copilot AI commented Jan 10, 2026

The CLIENT_* event names in the Bridge system were ambiguous—they refer to physical machines/containers connecting to the Bridge, not Discord clients.

Changes

  • Renamed three Bridge events:

    • CLIENT_CONNECTEDHOST_CONNECTED
    • CLIENT_DISCONNECTEDHOST_DISCONNECTED
    • CLIENT_STOPHOST_STOP
  • Updated BridgeEventListeners type definition and all event triggers in Bridge.ts

This affects the public API for Bridge event listeners:

// Before
bridge.on('CLIENT_CONNECTED', (client: BridgeClientConnection) => { ... });

// After
bridge.on('HOST_CONNECTED', (client: BridgeClientConnection) => { ... });
Original prompt

This section details on the original issue you should resolve

<issue_title>Rename CLIENT to HOST</issue_title>
<issue_description>The usage of CLIENT is very confusing.
To make it clear what is meant, the CLIENT-Keyword should be renamed to HOST since a physical machine/container is meant.</issue_description>

Comments on the Issue (you are @copilot in this section)


✨ Let Copilot coding agent set things up for you — coding agent works faster and does higher quality work when set up for your repo.

Copilot AI changed the title [WIP] Rename CLIENT keyword to HOST for clarity Rename CLIENT events to HOST in Bridge event system Jan 10, 2026
Copilot AI requested a review from Nevercold January 10, 2026 00:42
@Nevercold Nevercold requested a review from SleepyPxnda January 10, 2026 00:42
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Rename CLIENT to HOST

2 participants