Merge branch 'main' into next

Author: ivictbor

adminforth/dataConnectors/postgres.ts

@@ -6,6 +6,12 @@ import pkg from 'pg';
 import { afLogger, dbLogger } from '../modules/logger.js';
 
 const { Pool } = pkg;
+const { Client, types } = pkg;
+
+// postgres-date (used by pg for OID 1114/1082) parses no-TZ strings with new Date(y,m,d,...)
+// which treats them as LOCAL server time. Return raw strings so getFieldValue can parse as UTC.
+types.setTypeParser(1114, (val) => val); // TIMESTAMP WITHOUT TIME ZONE
+types.setTypeParser(1082, (val) => val); // DATE
 
 
 class PostgresConnector extends AdminForthBaseConnector implements IAdminForthDataSourceConnector {
@@ -200,7 +206,7 @@ class PostgresConnector extends AdminForthBaseConnector implements IAdminForthDa
                 return null;
             }
             if (field._underlineType == 'timestamp' || field._underlineType == 'int') {
-                return dayjs(value).toISOString();
+                return dayjs(value.replace(' ', 'T') + 'Z').toISOString();
             } else if (field._underlineType == 'varchar') {
                 return dayjs(value).toISOString();
             } else {
@@ -212,7 +218,7 @@ class PostgresConnector extends AdminForthBaseConnector implements IAdminForthDa
             if (!value) {
                 return null;
             }
-            return dayjs(value).toISOString().split('T')[0];
+            return value;
         }
 
         if (field.type == AdminForthDataTypes.BOOLEAN) {

adminforth/documentation/docs/tutorial/03-Customization/04-hooks.md

@@ -52,9 +52,9 @@ When user clicks the "Save" button on edit page, AdminForth makes a request to t
 
 ![Saving data on edit page](image-27.png)
 
-Practically you can use `edit.beforeSave` hook to modify the data or populate new fields before it is saved to the database.
+Practically you can use `hooks.edit.beforeSave` hook to modify the data or populate new fields before it is saved to the database.
 
-> 👆 Note: according to diagram you should understand that interrupting flow from `edit.afterSave` does not prevent data modification in DB
+> 👆 Note: according to diagram you should understand that interrupting flow from `hooks.edit.afterSave` does not prevent data modification in DB
 
 ## Saving data on create page
 
@@ -266,4 +266,4 @@ always performed before any hooks and any database requests.
 
 ## All hooks
 
-Check all hooks in the [API reference](/docs/api/Back/interfaces/AdminForthResource).
+Check all hooks in the [API reference](/docs/api/Back/interfaces/AdminForthResource).

adminforth/spa/src/components/Filters.vue

@@ -195,6 +195,7 @@ const props = defineProps<{
   filters?: AdminforthFilterStore['filters'],
   show: Boolean,
   columnsMinMax: ColumnMinMaxValue,
+  resourceId?: string,
   filtersStore: AdminforthFilterStoreUnwrapped
 }>();
 
@@ -235,7 +236,7 @@ async function loadMoreOptions(columnName: string, searchTerm = '') {
     columnName,
     searchTerm,
     columns: props.columns,
-    resourceId: router.currentRoute.value.params.resourceId as string,
+    resourceId: props.resourceId ?? router.currentRoute.value.params.resourceId as string,
     columnOptions,
     columnLoadingState,
     columnOffsets,

adminforth/spa/src/views/ListView.vue

@@ -7,6 +7,7 @@
         :show="filtersShow"
         @hide="filtersShow = false"
         :filtersStore="filtersStore"
+        :resourceId="coreStore.resource?.resourceId"
       />
     </Teleport>
 

live-demo/app/index.ts

@@ -8,6 +8,7 @@ import auditLogsResource from "./resources/auditLogs"
 import translations from "./resources/translations";
 import sessionsResource from './resources/agent_resources/sessions';
 import turnsResource from './resources/agent_resources/turns';
+import jobs_resource from './resources/jobs';
 import { randomUUID } from 'crypto';
 try { fs.mkdirSync('db') } catch (e) {} 
 
@@ -65,6 +66,7 @@ new AdminForth({
     translations,
     sessionsResource,
     turnsResource,
+    jobs_resource,
   ],
   menu: [
 

live-demo/app/migrations/20260429085926_add_background_jobs_plugin/migration.sql

@@ -0,0 +1,15 @@
+-- CreateTable
+CREATE TABLE "jobs" (
+    "id" TEXT NOT NULL PRIMARY KEY,
+    "created_at" DATETIME NOT NULL,
+    "finished_at" DATETIME,
+    "started_by" TEXT NOT NULL,
+    "name" TEXT NOT NULL,
+    "state" TEXT,
+    "progress" TEXT NOT NULL,
+    "status" TEXT NOT NULL,
+    "job_handler_name" TEXT NOT NULL
+);
+
+-- CreateIndex
+CREATE INDEX "translations_completedLangs_idx" ON "translations"("completedLangs");

live-demo/app/migrations/migration_lock.toml

@@ -1,3 +1,3 @@
 # Please do not edit this file manually
 # It should be added in your version-control system (e.g., Git)
-provider = "sqlite"
+provider = "sqlite"