Store DM file metadata in mongo db #99
Open
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
ThomasWu931
changed the title
dhrumilp15
changed the title
Owner
|
This is a good idea |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
Problem
Files provided in direct messages with the bot are not being stored within the mongo db client.
Solution
This issue is caused by these 2 chunks of code: one, and two. Since dms lack a
message.guildfield, an error will be raised in the 1st snippet because ur trying to accessmessage.guild.idin the first snippet. This raises an error in the console and prevents dm files from being saved within the mongoDB client. However, this error isn't caught because the 2nd snippet ignores the error in try-except block.Solution is to rewrite the ternary operator in snipper one.
Next Steps
NA