fix: Ensure guild settings exist in DB before updating #999
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
If a user switches branches or changes schema.prisma without running `npm install` the generated client will be out of sync with the schema. Adding a npm run script makes doing this easier without needing to have primsa installed globally.
If a user: * runs muse and adds the bot to their guild * deletes database (EX recreates docker container) * runs muse and tries to update config before doing anything else Then muse tries to update settings that were not created since guild-create event was not fired due to bot already existing in user's guild. Fix this by always getting/creating guild settings before updating any from config command
📦 A new release has been made for this pull request.To play around with this PR, pull Images are available for x86_64 and ARM64.
|
|
thanks! |
|
🚀 Released in Release v2.6.0. |
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.
If a user:
Then muse tries to update settings that were not created since guild-create event was not fired due to bot already existing in user's guild.
Fix this by always getting/creating guild settings before updating any from config command