Adapt next-adapter to work with slash API #354

enonic · Oct 30, 2023 · 1b93024 · 1b93024
1 parent 5c7f190
commit 1b93024
Show file tree

Hide file tree

Showing 7 changed files with 119 additions and 96 deletions.
diff --git a/package-lock.json b/package-lock.json
diff --git a/package.json b/package.json
@@ -15,7 +15,7 @@
   "dependencies": {
     "html-react-parser": "^4.2.9",
     "lru-cache": "^10.0.1",
-    "next": "13.5.6",
+    "next": "13.4.12",
     "react": "18.2.0",
     "react-dom": "18.2.0",
     "unescape": "^1.0.1"

diff --git a/src/ComponentRegistry.ts b/src/ComponentRegistry.ts
@@ -36,15 +36,12 @@ interface ComponentDictionary {
 // NB! Always return null or empty object from processor for next is unable to serialize undefined
 export type DataProcessor = (data: any, context?: Context, config?: any) => Promise<Record<string, any>>;
 
-// TODO: also access as arguments: dataAsJson, pageAsJson, configAsJson from the first (meta) call here?
-//   Another option could be to let the component or page controller pass those values to NextJS by a header
 export type VariablesGetter = (path: string, context?: Context, config?: any) => VariablesGetterResult;
 
 export type QueryGetter = (path: string, context?: Context, config?: any) => string;
 
 export type VariablesGetterResult = {
     [variables: string]: any,
-    path: string,
 };
 
 export type SelectedQueryMaybeVariablesFunc = string | QueryGetter |