Rename CLIENT events to HOST in Bridge event system #5
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.
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_CONNECTED→HOST_CONNECTEDCLIENT_DISCONNECTED→HOST_DISCONNECTEDCLIENT_STOP→HOST_STOPUpdated
BridgeEventListenerstype definition and all event triggers inBridge.tsThis affects the public API for Bridge event listeners:
Original prompt
CLIENTtoHOST#1✨ Let Copilot coding agent set things up for you — coding agent works faster and does higher quality work when set up for your repo.