Prevent query from returning cached data when using skipToken

[JosNun]

Is there a way to prevent a query from returning cached data when I'm passing skipToken as the arg? In my case, between selected items, a parameter changes from a to undefined to b, and while b is still fetching, the data field returned from the query is the value of a.

Ie, in the following example, if routeParams.code is A, then code changes to undefined, then code changes to B, while the data for B is fetching, data will contain the data for A.

const { data } =
    useGetItemByCodeQuery(
        routeParams.code
            ? {
                  code: routeParams.code,
              }
            : skipToken
    );
    
console.log(routeParams.code, data);
// a, {code: a}
// undefined, {code: a}
// b, {code: a}
// b, {code: b}

A potential workaround is utilizing the isUnitialized value returned from a query, but in my particular case, I have multiple queries dependent on the first, so there'll be a handful of isInitialized variables that'll need to be juggled so as not to show data for a different item.

[phryneas]

Not at the moment. You can only do something like

const arg = routeParams.code ? { code: routeParams.code }  : skipToken
const { data } = useGetItemByCodeQuery(arg);
const myData = arg == skipToken ? undefined : data

[JosNun]

Thanks! I ended up doing something similar, it just felt a little unergonomic, but I guess this isn't that common of a use case. Thanks again!