fix: force guild recache from GUILD_CREATE #104
Merged
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.
Summary
Adds an option to
ensure_server
to force the recache of a guild. This is necessary because there is a window in this cache lifecycle where we can have a server object with bad state that permanently occupies the cache.Added
Cache#ensure_server
- Addforce_recache
parameter to ensure guilds fromGUILD_CREATE
are used as the source of truth.Changed
Server#update_data
- Move data initialization logic frominitialize
toupdate_data
for reusability.