Opt-out of serverCacheKey

[urbnjamesmi1]

What problem does this feature solve?

Being able to decide at runtime if a component should be cached on the server.

For example, if I have a re-usable ImageViewer component that I only want cached in certain use cases.

import { get } from 'lodash-es';
export default {
    name: 'ImageViewer',
    serverCacheKey: (props) => get(props, 'images.0.id'),
    props: {
        images: {
            type: Array,
            required: true
        }
    }
};

It would be preferred to be able to return undefined from the serverCacheKey function and know that the component won't be cached. Currently, it would be cached by its name and would collide with any other uses of the component that also returned undefined.

What does the proposed API look like?

The same API for the existing serverCacheKey that takes the props object, but allow for returning undefined to indicate, to skip looking for the component in the server renderer cache (even if the component has a name).

[posva]

I think an explicit false rather than undefined makes more sense, but null and undefined also look like an invalid key

[urbnjamesmi1]

Sounds good. Just looking for a way to conditionally prevent caching.

[yyx990803]

Closed via ab24285