feat(backend): caching middleware - #575
Draft
jaskfla wants to merge 2 commits into
Draft
Conversation
jaskfla
force-pushed
the
cache-discord-reqs
branch
from
May 19, 2026 21:26
1031389 to
9abb2cc
Compare
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
Important
Currently missing a mechanism for cache invalidation. Also not tested.
If we accept this proposal, then the caching of Discord API requests introduced in #574 becomes redundant, because those are all
GETrequests anyway.Stacked on #574, but primarily because that branch has the custom
Cacheclass which this bit of middleware depends on.🥞 Stack