Merge branch 'next' of github.com:devforth/adminforth into next

Author: SerVitasik

adminforth/documentation/docs/tutorial/01-helloWorld.md

@@ -131,7 +131,8 @@ Create `index.ts` file in root directory with following content:
 
 ```ts title="./index.ts"
 import express from 'express';
-import AdminForth, { AdminForthDataTypes, AdminUser, Filters } from 'adminforth';
+import AdminForth, { AdminForthDataTypes, Filters } from 'adminforth';
+import type { AdminForthResourceInput, AdminForthResource, AdminUser } from 'adminforth';
 
 export const admin = new AdminForth({
   baseUrl: '',
@@ -208,6 +209,26 @@ export const admin = new AdminForth({
         },
         { name: 'passwordHash', backendOnly: true, showIn: { all: false } }
       ],
+      hooks: {
+        create: {
+          beforeSave: async ({ record, adminUser, resource }: { record: any, adminUser: AdminUser, resource: AdminForthResource }) => {
+            record.password_hash = await AdminForth.Utils.generatePasswordHash(record.password);
+            return { ok: true };
+          }
+        },
+        edit: {
+          beforeSave: async ({ oldRecord, updates, adminUser, resource }: { oldRecord: any, updates: any, adminUser: AdminUser, resource: AdminForthResource }) => {
+            console.log('Updating user', updates);
+            if (oldRecord.id === adminUser.dbUser.id && updates.role) {
+              return { ok: false, error: 'You cannot change your own role' };
+            }
+            if (updates.password) {
+              updates.password_hash = await AdminForth.Utils.generatePasswordHash(updates.password);
+            }
+            return { ok: true }
+          },
+        },
+      }
     },
     {
       table: 'post',

adminforth/documentation/docs/tutorial/03-Customization/06-customPages.md

@@ -457,10 +457,18 @@ You can navigate user to this page using any router link, e.g.:
 </template>
 ```
 
+Add to your `<script setup>` section:
+
 ```ts
 import { Link } from '@/afcl';
 ```
 
+If you set `customLayout: true` in the `meta` object, it will not include default layout like sidebar and header, so you can create your own layout for this page. 
+
+> **Redirects to login page**: Any route which has sidebar and header (e.g. default CRUD pages or menu item with `component`) uses internal AdminForth REST API to fetch menu items and user information, so it passes authentication check and if authentication cookie is not provided or has expired JWT user gets redirected to the login page.
+> In case if you set `customLayout: true`, it will not call these APIs so user will not be automatically redirected to the login page in case of expired or not-provided authentication cookie. That feature allows you to implement public pages without authentication, e.g. Terms of Service, Privacy Policy and many others. In case if you need to check if user is logged in just call any custom API which has `admin.express.authorize` middleware. Obviously for public pages you should create API endpoint WITHOUT `admin.express.authorize` middleware.
+
+
 ### Passing meta attributes to the page
 
 

adminforth/documentation/docs/tutorial/05-Plugins/15-ForeignInlineShow.md

@@ -0,0 +1,67 @@
+
+Allows to add an inline show of connected foreign resource records on a adminforth show page.
+
+Foreign inline show plugin allows to display a show of items from a foreign table in the show view.
+
+## Usage
+
+
+Import plugin:
+
+```bash
+npm i @adminforth/foreign-inline-show --save
+```
+
+```ts title="./resources/adminuser.ts"
+import ForeignInlineShowPlugin from '@adminforth/foreign-inline-show';
+import { AdminForthResource, AdminForthResourceColumn } from 'adminforth';
+```
+
+
+In [Getting Started](<../001-gettingStarted.md>) we created a `'aparts'` resource which has a field `'realtor_id'`.
+This field refers to record from `'adminuser'` resource. To remind you, we configured this relation using `foreignResource` setting in the column configuration:
+
+```typescript title="./resources/apartments.ts"
+// 
+export default {
+  resourceId: 'aparts',
+  ...
+  columns: [
+    ...
+    {
+      name: 'realtor_id',
+      foreignResource: {
+        resourceId: 'adminuser',  // this means that aparts.realtor_id refers to primary key of 'adminuser' resource
+                              // this is Many-To-One relatin: many aparts can refer to one user
+      }
+    }
+  ],
+}
+```
+
+This means that we can display a show of user in the apartments show view.
+
+Add to your `'apartments'` resource configuration the plugin instance:
+
+```ts title="./resources/apartments.ts"
+{ 
+    ...
+    resourceId: 'aparts',
+    ...
+//diff-add
+    plugins: [
+//diff-add
+      new ForeignInlineShowPlugin({
+//diff-add
+        foreignResourceId: 'users',
+//diff-add
+      }),
+//diff-add
+    ],
+}
+```
+
+![alt text](ForeignInlineShow.png)
+
+> 👆 To make plugin work, the specified resource (defined with `foreignResourceId`) should have one (and only one) column that refers to the current resource on which you add a plugin.
+> In our case we add plugin to `adminuser` resource, so the `aparts` resource should have one column with `foreignResource.resourceId` equal to `adminuser` resourceId.