change users config file name to adminuser

Author: Petr Kachanovsky

adminforth/commands/createApp/templates/users.ts.hbs renamed to adminforth/commands/createApp/templates/adminuser.ts.hbs

@@ -1,6 +1,6 @@
 import express from 'express';
 import AdminForth, { Filters } from 'adminforth';
-import usersResource from "./resources/users";
+import usersResource from "./resources/adminuser";
 
 const ADMIN_BASE_URL = '';
 

adminforth/commands/createApp/templates/index.ts.hbs

@@ -191,8 +191,8 @@ async function writeTemplateFiles(dirname, cwd, options) {
       data: { dbUrl, prismaDbUrl },
     },
     {
-      src: 'users.ts.hbs',
-      dest: 'resources/users.ts',
+      src: 'adminuser.ts.hbs',
+      dest: 'resources/adminuser.ts',
       data: {},
     },
     {

adminforth/commands/createApp/utils.js

@@ -325,9 +325,9 @@ if (import.meta.url === `file://${process.argv[1]}`) {
 
 ## Step 5: Create resources
 
-Create `res` folder. Create `./res/user.ts` file with following content:
+Create `res` folder. Create `./res/adminuser.ts` file with following content:
 
-```ts title="./res/users.ts"
+```ts title="./res/adminuser.ts"
 import AdminForth, { AdminForthDataTypes } from 'adminforth';
 import { randomUUID } from 'crypto';
 import UploadPlugin from '@adminforth/upload';

adminforth/documentation/blog/2024-10-01-ai-blog/index.md

@@ -64,7 +64,7 @@ myadmin/
 │   ├── package.json      # For any custom npm packages you will use in Vue files
 │   └── tsconfig.json     # Tsconfig for Vue project (adds completion for AdminForth core components)
 ├── resources
-│   └── users.ts          # Example resource file for users management
+│   └── adminuser.ts      # Example resource file for users management
 ├── schema.prisma         # Prisma schema file for database schema
 ├── index.ts              # Main entry point: configures AdminForth & starts the server
 ├── package.json          # Project dependencies

adminforth/documentation/docs/tutorial/001-gettingStarted.md

@@ -84,7 +84,7 @@ Another usecase of `virtual` columns is to add new fields in edit and create vie
 Thing is that password itself can't be stored in the database, but instead their hash is stored. 
 So we need to add `password` field to the `adminuser` resource and make it `virtual` so it will not be stored in the database.
 
-```ts title="./resources/users.ts"
+```ts title="./resources/adminuser.ts"
 ...
 resourceId: 'adminuser',
 ...

adminforth/documentation/docs/tutorial/03-Customization/03-virtualColumns.md

@@ -15,7 +15,7 @@ You can use `options.allowedActions` on resource to limit access to the resource
 
 If you want to disable deletion of the resource records for all users:
 
-```ts title="./resources/users.ts"
+```ts title="./resources/adminuser.ts"
 {
   ...
   resourceId: 'adminuser',
@@ -69,7 +69,7 @@ import type { AdminUser } from  'adminforth';
 
 Let's disable creating and editing of new users for all users apart from users with role `superadmin`, and at the same time disable deletion for all users:
 
-```ts title="./resources/users.ts"
+```ts title="./resources/adminuser.ts"
 //diff-add
 import type { AdminUser } from  'adminforth';
 

adminforth/documentation/docs/tutorial/03-Customization/05-limitingAccess.md

@@ -346,7 +346,7 @@ export default {
 In cases when column values must follow certain format, you can add `validation` to it.
 `validation` is an array of rules, each containing `regExp` that defines a format for a value and `message` that will be displayed in case when entered value does not pass the check.
 
-```typescript title="./resources/users.ts"
+```typescript title="./resources/adminuser.ts"
 export default {
       name: 'adminuser',
       columns: [
@@ -374,7 +374,7 @@ export default {
 
 You can add `editingNote` to a column to show a note below the input field.
 
-```typescript title="./resources/users.ts"
+```typescript title="./resources/adminuser.ts"
 export default {
       name: 'adminuser',
       columns: [
@@ -393,7 +393,7 @@ export default {
 
 Whenever you want to have a column to store not a single value but an array of values you have to set column as `AdminForthDataTypes.JSON`. This way when you are creating or editing a record you can type in a JSON array into a textfield. To simplify this process and allow you to create and edit separate items you can add `isArray` to a column.
 
-```typescript title="./resources/users.ts"
+```typescript title="./resources/adminuser.ts"
 export default {
       name: 'adminuser',
       columns: [
@@ -422,7 +422,7 @@ Doing so, will result in UI displaying each item of the array as a separate inpu
 
 By default it is forbidden to store duplicate values in an array column. To change that you can add `allowDuplicateItems: true` to `isArray`, like so:
 
-```typescript title="./resources/users.ts"
+```typescript title="./resources/adminuser.ts"
 export default {
       name: 'adminuser',
       columns: [
@@ -452,7 +452,7 @@ Note: array columns can not be marked as `masked`, be a `primaryKey` and at the
 
 When you want to create a connection between two resources, you need to add `foreignResource` to a column, like so:
 
-```typescript title="./resources/users.ts"
+```typescript title="./resources/adminuser.ts"
 export default {
       name: 'adminuser',
       columns: [

adminforth/documentation/docs/tutorial/03-Customization/13-standardPagesTuning.md

@@ -10,14 +10,14 @@ npm i @adminforth/two-factors-auth --save
 
 Plugin is already installed into adminforth, to import:
 
-```ts title="/users.ts"
+```ts title="/adminuser.ts"
 import TwoFactorsAuthPlugin from '@adminforth/two-factors-auth';
 ```
 
 Plugin required some additional setup, to make it work properly. It should be added to the resource auth resource. In our example we will add it to the user resource .
 
 ```ts title='./schema.prisma'
-model users {
+model adminuser {
   id            String     @id
   created_at    DateTime
   email         String   @unique
@@ -34,9 +34,9 @@ Then:
 npx --yes prisma migrate dev --name init
 ```
 
-And add it to `users.ts`
+And add it to `adminuser.ts`
 
-```ts tittle="./resources/users.ts"
+```ts tittle="./resources/adminuser.ts"
 {
     table: 'adminuser',
 //diff-add
@@ -108,7 +108,7 @@ By default plugin enforces Two-Factor Authentication for all users.
 
 If you wish to enforce 2FA only for specific users, you can again use `usersFilterToApply` option:
 
-```ts title='./users.ts'
+```ts title='./adminuser.ts'
   usersFilterToApply: (adminUser: AdminUser) => {
     // disable 2FA for users which email is 'adminforth' or 'adminguest'
     return !(['adminforth', 'adminguest'].includes(adminUser.dbUser.email));
@@ -117,7 +117,7 @@ If you wish to enforce 2FA only for specific users, you can again use `usersFilt
 
 You can even add a boolean column to the user table to store whether the user should use 2FA or not:
 
-```ts title='./users.ts'
+```ts title='./adminuser.ts'
 {
     resourceId: 'adminuser',
     ...
@@ -162,7 +162,7 @@ By default, all users are required to setup Two-Factor Authentication.
 
 If you want to allow specific users to skip the 2FA setup, you can use the `usersFilterToAllowSkipSetup` option:
 
-```ts title='./users.ts'
+```ts title='./adminuser.ts'
 ...
 plugins: [
         new TwoFactorsAuthPlugin ({

adminforth/documentation/docs/tutorial/05-Plugins/02-TwoFactorsAuth.md

@@ -10,7 +10,7 @@ Import plugin:
 npm i @adminforth/foreign-inline-list --save
 ```
 
-```ts title="./resources/users.ts"
+```ts title="./resources/adminuser.ts"
 import ForeignInlineListPlugin from '@adminforth/foreign-inline-list';
 import { AdminForthResource, AdminForthResourceColumn } from 'adminforth';
 ```
@@ -42,7 +42,7 @@ This means that we can display a list of apartments in the user's show view.
 Add to your `'adminuser'` resource configuration the plugin instance:
 
 
-```ts title="./resources/users.ts"
+```ts title="./resources/adminuser.ts"
 { 
     ...
     resourceId: 'adminuser',