next/dist/esm/client/components/router-reducer/create-segment-key.js

The React Framework

import { createRouterCacheKey } from './create-router-cache-key';
// React uses these keys to find suspended subtrees when resuming HTML. They
// must be the same before and after route params and search params are known.
// The browser uses the concrete keys instead, so navigation still resets or
// preserves state as appropriate. Its bundle uses create-segment-key.browser.ts.
// React keys are not embedded in the HTML.
export function createSegmentKey(segment) {
    if (Array.isArray(segment)) {
        return `${segment[0]}|${segment[2]}`;
    }
    return createRouterCacheKey(segment);
}
// TODO: To model this more accurately, we should use React.optimisticKey
// instead. Perhaps a separate Fragment that wraps around the Head:
// <Fragment key={headKey}> where headKey is React.optimisticKey during
// SSR. We should do this for all fallback param values.
export function createHeadKey(varyPath) {
    // The head's vary path starts with its request key: the route structure,
    // with param names but no values.
    return varyPath.value;
}

//# sourceMappingURL=create-segment-key.js.map