feat: disable auto-resolve and memory caching when cache is off #296
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.
These changes unify “reduce extra requests when cache is disabled” under a single flag and prevent in‑memory caching when cache is off. A new DisableAutoResolve is introduced (auto‑enabled when DisableCache is true), so message processing no longer fetches min users/channels from the server, and all cache fetch paths become cache‑only in that mode. Cache updates are also skipped when disabled, ensuring no file writes and no in‑memory retention.
Files touched:
client.go: add/enable DisableAutoResolve with DisableCache
helpers.go: skip min user/channel auto resolve; getSender is cache‑only
cache.go: skip memory updates when disabled; cache fetches are cache‑only under DisableAutoResolve