fix: 空のメッセージに反応するバグを修正 #363
Merged
Conversation
This file contains 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
MikuroXina
force-pushed
the
fix/embed-reaction
branch
from
4ba3945
to
d6f143d
Compare
Codecov Report
@@ Coverage Diff @@
## main #363 +/- ##
==========================================
- Coverage 69.31% 69.25% -0.06%
==========================================
Files 53 53
Lines 3484 3487 +3
Branches 331 331
==========================================
Hits 2415 2415
- Misses 738 741 +3
Partials 331 331
Flags with carried forward coverage won't be shown. Click here to find out more.
Help us with your feedback. Take ten seconds to tell us how you rate us. |
m1sk9
approved these changes
Jul 30, 2022
|
🎉 This PR is included in version 1.22.0 🎉 The release is available on GitHub release Your semantic-release bot 📦🚀 |
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.
Type of Change:
コードのバグ修正
Details of implementation (実施内容)
Discord.js のバージョン更新の際に, メッセージ本文が
nullの代わりに''になることがある仕様変更を確認していました. しかし, それに起因するバグが発生したため検知して弾くようにコードを修正しました.