@se-studio/project-build 1.0.65 → 1.0.67
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
package/CHANGELOG.md
CHANGED
package/package.json
CHANGED
|
@@ -91,7 +91,7 @@ export default async function (props: PageProps<'/[level1]'>) {
|
|
|
91
91
|
}
|
|
92
92
|
```
|
|
93
93
|
|
|
94
|
-
For article routes, use `converterContext.urlCalculators.article`, `articleType`, `articleTypeTag` from `@/lib/cms-server
|
|
94
|
+
For article routes, use `converterContext.urlCalculators.article`, `articleType`, `articleTypeTag` to compute the path. Import `converterContext` from `@/lib/converter-context` when that module exists (so route files don't pull in cms-server); otherwise from `@/lib/cms-server`.
|
|
95
95
|
|
|
96
96
|
## See Also
|
|
97
97
|
|
|
@@ -101,6 +101,8 @@ The appShared modules render content with:
|
|
|
101
101
|
- `rendererConfig` – from `@/lib/cms-server`
|
|
102
102
|
- `pageContext` – provides page/article/customType to child components
|
|
103
103
|
|
|
104
|
+
For route files that only need `converterContext` or `buildInformation` (e.g. `generateStaticParams`, sitemap, path computation), import from `@/lib/converter-context` when that module exists, so you don't pull in cms-server.
|
|
105
|
+
|
|
104
106
|
## Creating a Specialized Route
|
|
105
107
|
|
|
106
108
|
For a route that behaves differently from standard CMS pages (e.g. search, dashboard):
|