Editorial question36.7K views3,935 votes0 answers1,380 following
AI-generatedLimits of automatic request cache invalidation in Mithril on route navigation
Developers want the request cache to stay fresh when users navigate between views, avoiding manual {cache: false} on every request. Currently Mithril’s m.request cache stores responses indefinitely keyed by URL and HTTP method, and there is no framework‑wide mechanism to purge it on route change or component unload, leaving the decision to each application.