TransferHttpCacheModule not taking request params into account

There seems to be an issue with TransferHttpCacheModule sending the previous request to the server. When I navigating to and from different product categories I will some get the wrong response returned i.e I’ll get results for the last category I visited rather than the one it supposed to return.

I can see the value from route.paramMap is changing but the server is not receiving that value it get the last value.

So I’m believe it because the cache isn’t taking the change in params into account and assume it’s the same request

export class ShopListResolver implements Resolve<any> {
  constructor(private service: ApiService, private router: Router) {
    service.endpoint = 'productdisplay';
  }

  resolve(
    route: ActivatedRouteSnapshot,
    state: RouterStateSnapshot
  ): Observable<any> {
    const category = route.paramMap.get('category');
    return this.service
      .find({
        $category: category,
        published: true,
        $sort: ['weight'],
        $select: ['title', 'listing_image', 'product_type', 'slug']
      })
      .pipe(take(1));
  }
}

[CaerusKaru]

I understand the merit for a GraphQL-like functionality. Unfortunately we cannot build this functionality for everyone just to satisfy GraphQL users. My recommendation is to implement your own interceptor based on the code in this library, with special accommodations for GraphQL.

[dottodot]

Is there any reason why req.urlWithParams couldn’t be used rather than req.url