Skip to content
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 our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Allow dropping a user not in the server #466

Merged
merged 4 commits into from
Feb 1, 2023
Merged

Conversation

AlphaKretin
Copy link
Contributor

Description

Handle when their Member data doesn't exist
Relevant to #465, though doesn't close it entirely

Checklist

Handle when their Member data doesn't exist
@AlphaKretin
Copy link
Contributor Author

While testing, the schema edit caused issues on my end, so we're gonna have to figure that out when we merge

@kevinlul
Copy link
Contributor

Is synchronize bad at mutating SQLite tables?

@kevinlul
Copy link
Contributor

kevinlul commented Feb 1, 2023

synchronize will be fine as long as there is no data in the deck table, due to the non-null constraint on the new column

Cannot error, guild will be guaranteed cached, left users will just fall back to the user data
src/slash/forcedrop.ts Outdated Show resolved Hide resolved
@AlphaKretin AlphaKretin merged commit 2881f64 into master Feb 1, 2023
@AlphaKretin AlphaKretin deleted the drop-left-player branch February 1, 2023 02:39
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants