We discussed this in our previous dev meeting regarding how template-partshandles post types. Currently, default post template as "single" template key. As a result, the system fails to resolve this specific template and falls back incorrectly.
|
const type = `single-${node.__typename}`.toLowerCase(); |
Proposed Change:
const getTemplateData = async (node: any) => {
const type = node.__typename === 'post' ? 'single' : `single-${node.__typename}`.toLowerCase();
const { getData } = templatesDataList?.[type] ?? {};
if (!getData) return {};
return await getData(fetchAPI, node);
};
```
We discussed this in our previous dev meeting regarding how template-partshandles post types. Currently, default post template as "single" template key. As a result, the system fails to resolve this specific template and falls back incorrectly.
superstack/next/src/lib/get-node-by-uri.ts
Line 211 in 559e4dd
Proposed Change: