Ionic Angular HttpClient concurrent GET request deduplication

Ionic Angular applications using HttpClient do not include a built-in mechanism to deduplicate identical in-flight GET requests. When multiple components trigger the same request within a short window, each request is sent independently to the server.

The framework level provides no default caching or request coalescing, so deduplication must be considered at the application configuration layer, typically via an interceptor or external library. The decision boundary is unclear regarding whether deduplication should be global, module scoped, or opt-in per request, and what permission constraints should apply to cache keys and response reuse.

Documentation does not specify a planned default behavior for automatic request deduplication in future Ionic releases, leaving the choice to project teams.

Should request deduplication be treated as a framework-provided configuration option or remain an application-level concern? What permission boundary should govern which requests are eligible for coalescing? Is there a documented stance on default deduplication behavior for Ionic Angular HttpClient?