Merge master #11
Merged
Merge master #11
Conversation
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
It's better to clearly instruct new users that outgoing messages will cause a 'message' event emit in order to prevent infinitely sending messages Co-authored-by: Huan (李卓桓) <zixia@zixia.net>
* Update wechaty.ts Remove `room.sync()`, because it can not get room info when the bot has been removed from room. * restore sync in room I agree with @windmemory that there should be a flag to let user know that this room has died. * restore.. wtf the bug? * clean * clean Co-authored-by: Huan (李卓桓) <zixia@zixia.net>
* feat delay friendship accept * test * change toJson() -> to JSON() Co-authored-by: Huan (李卓桓) <zixia@zixia.net>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
I'm submitting a...
Checklist
Description
please describe the changes that you are making
for features, please describe how to use the new feature
please include a reference to an existing issue, if applicable
Does this PR introduce a breaking change?