Movatterモバイル変換


[0]ホーム

URL:


Skip to content

Navigation Menu

Sign in
Appearance settings

Search code, repositories, users, issues, pull requests...

Provide feedback

We read every piece of feedback, and take your input very seriously.

Saved searches

Use saved searches to filter your results more quickly

Sign up
Appearance settings

feat: 🎸 implement room announce#2527

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 ourterms of service andprivacy statement. We’ll occasionally send you account related emails.

Already on GitHub?Sign in to your account

Open
hcfw007 wants to merge1 commit intowechaty:main
base:main
Choose a base branch
Loading
fromjuzibot:feat/room-announce-wechaty

Conversation

@hcfw007
Copy link
Member

@hcfw007hcfw007 commentedApr 26, 2023
edited by ellipsis-devbot
Loading

issue:#2524

由于相关 PR 尚未 merge , CI 无法通过。


🚀 This description was created byEllipsis for commit5d2ce40

Summary:

Implements theroom-announce event handling in Wechaty, updating event schemas and the puppet mixin to support room announcement notifications.

Key points:

  • AddedRoomEventListenerAnnounce in/src/schemas/room-events.ts.
  • IntroducedWechatyEventListenerRoomAnnounce in/src/schemas/wechaty-events.ts.
  • Implemented event handling forroom-announce in/src/wechaty-mixins/puppet-mixin.ts.
  • Ensured proper event propagation and error handling for the new event type.

Generated with ❤️ byellipsis.dev

ellipsis-dev[bot] reacted with rocket emoji
typeWechatyEventListenerRoomTopic=(room:RoomInterface,newTopic:string,oldTopic:string,changer:ContactInterface,date?:Date)=>void|Promise<void>
typeWechatyEventListenerScan=(qrcode:string,status:PUPPET.types.ScanStatus,data?:string)=>void|Promise<void>
typeWechatyEventListenerStartStop=()=>void|Promise<void>
typeWechatyEventListenerRoomAnnounce=(room:RoomInterface,newAnnounce:string,changer:ContactInterface,oldAnnounce?:string,date?:Date)=>void|Promise<void>
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others.Learn more.

Please keep the parameters order the same as theWechatyEventListenerRoomTopic

@huan
Copy link
Member

huan commentedMay 3, 2024

Hey@ellipsis, give me a code review

ellipsis-dev[bot] reacted with eyes emoji

@ellipsis-dev
Copy link

OK! Reviewing this PR...


Responding tothis comment by@huan. For more information about Ellipsis, check thedocumentation.

@dosubotdosubotbot added the size:MThis PR changes 30-99 lines, ignoring generated files. labelMay 3, 2024
Copy link

@ellipsis-devellipsis-devbot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others.Learn more.

👍 Looks good to me!

  • Reviewed the entire pull request up to5d2ce40
  • Looked at124 lines of code in3 files
  • Took 1 minute and 9 seconds to review
More info
  • Skipped0 files when reviewing.
  • Skipped posting3 additional comments because they didn't meet confidence threshold of50%.
1.src/schemas/room-events.ts:113:
  • Assessed confidence :0%
  • Comment:
    The implementation of theRoomEventListenerAnnounce and its addition to theRoomEventListeners interface is correctly done, matching the existing patterns for event listeners in the system.
  • Reasoning:
    The PR introduces a new event typeroom-announce in theRoomEventListeners interface and the corresponding event listener typeRoomEventListenerAnnounce. The event listener type is defined correctly with appropriate parameters including the room, the new announcement, the changer, the old announcement, and the date. This aligns with the typical structure of event listeners in the system, which usually include the main object (room), the primary change (newAnnounce), the initiator of the change (changer), and optionally the previous state (oldAnnounce) and the timestamp (date).
2.src/schemas/wechaty-events.ts:210:
  • Assessed confidence :0%
  • Comment:
    The implementation of theWechatyEventListenerRoomAnnounce and its addition to theWechatyEventListeners interface is correctly done, matching the existing patterns for event listeners in the system.
  • Reasoning:
    The PR introduces a new event typeroom-announce in theWechatyEventListeners interface and the corresponding event listener typeWechatyEventListenerRoomAnnounce. The event listener type is defined correctly with appropriate parameters including the room, the new announcement, the changer, the old announcement, and the date. This aligns with the typical structure of event listeners in the system, which usually include the main object (room), the primary change (newAnnounce), the initiator of the change (changer), and optionally the previous state (oldAnnounce) and the timestamp (date).
3.src/wechaty-mixins/puppet-mixin.ts:421:
  • Assessed confidence :0%
  • Comment:
    The implementation of theroom-announce event handling in thepuppetMixin class is correctly done, following the established patterns for similar event handlers in the system.
  • Reasoning:
    The PR introduces handling for theroom-announce event in thepuppetMixin class. The handling logic includes finding the room and the changer based on their IDs, syncing the room, and emitting both a Wechaty and a room-specific event with the new announcement, the changer, the old announcement, and the date. This follows the typical pattern for event handling in the system, which involves resource lookup, state synchronization, and event emission with relevant data.

Workflow ID:wflow_UOORNsxRCg07wnkl


You can customize Ellipsis with review rules, user-specific overrides,quiet mode, and more. Seedocs.

6 days left in your free trial,upgrade for $20/seat/month orcontact us.

Sign up for freeto join this conversation on GitHub. Already have an account?Sign in to comment

Reviewers

@ellipsis-devellipsis-dev[bot]ellipsis-dev[bot] left review comments

@huanhuanhuan requested changes

Requested changes must be addressed to merge this pull request.

Assignees

No one assigned

Labels

size:MThis PR changes 30-99 lines, ignoring generated files.

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

2 participants

@hcfw007@huan

[8]ページ先頭

©2009-2025 Movatter.jp