@live-change/frontend-template 0.9.206 → 0.9.207

package/.claude/rules/live-change-backend-actions-views-triggers.md

@@ -16,6 +16,12 @@ Use these rules when implementing actions, views, and triggers in LiveChange ser
   - use indexes instead of full scans,
   - return a meaningful result (ids, data, etc.).
 
+### Validation and `if`
+
+- Treat property-level `if` as the condition for both visibility and validation.
+- Backend auto-validation skips validators for fields where `if` resolves to `false`.
+- For conditional required fields, keep validators on the field and model the condition with `if`, instead of duplicating the same guard in multiple action handlers.
+
 Example:
 
 ```js

package/.claude/skills/live-change-design-actions-views-triggers/SKILL.md

@@ -35,6 +35,12 @@ Use this skill to design **actions, views, and triggers** in LiveChange services
    - session keys,
    - any data needed for the next step.
 
+### Validation and `if`
+
+- Define conditional fields with property-level `if` directly on the schema field.
+- Runtime validation skips fields where `if` evaluates to `false` (frontend `validateData` and backend auto-validation).
+- Keep the validator list (`validation`, `softValidation`) on the field itself, and avoid duplicating the same condition in ad-hoc `execute` guards unless business logic requires additional checks.
+
 Example:
 
 ```js

package/.claude/skills/live-change-design-models-relations/SKILL.md

@@ -20,10 +20,14 @@ For each new model, decide how it relates to the rest of the domain:
 - **`userItem`** – the object belongs to the signed-in user (e.g. user’s device).
 - **`itemOf`** – a list of children belonging to a parent model (e.g. device connections).
 - **`propertyOf`** – a single state object with the same id as the parent (e.g. cursor state).
+- **`entity`** – global / role-scoped; do **not** pair with manual **`owner`** when **`userItem`** fits “my rows” for `client.user`.
+- **`sessionOrUserItem`** / **`sessionOrUserProperty`** – owner is Session **or** User (no **`sessionItem`** annotation).
 - **no relation** – for global data or other special cases.
 
 Choose one main relation; other associations can be plain fields + indexes.
 
+Decision guide: **`docs/docs/server/09-07-owner-selection-useritem.md`**.
+
 ## Step 2 – Define `properties` clearly
 
 1. Use a **multi-line** style for properties, with clear `type`, `default`, `validation`, etc.
@@ -62,6 +66,30 @@ properties: {
 }
 ```
 
+## Property validation (validators)
+
+- Built-in validator names live in `@live-change/framework/lib/utils/validators.js`. Do not invent names that are not there unless you also register them.
+- Common patterns: `validation: ['nonEmpty']`, strings with `{ name: 'maxLength', length: 80 }`, numbers with `['number', 'integer', { name: 'min', value: 0 }, { name: 'max', value: 999 }]`.
+- **Service-defined validators:** `definition.validator('email', factory)` (see `email-service/index.js` + `emailValidator.js`). Validators are merged across services at startup — avoid name clashes.
+- **Frontend:** assign client factories to `api.validators` under the same keys (e.g. `clientEmailValidator.js` in `App.vue`). Match server error codes for i18n.
+- Full reference: server manual page **Property validation** (`docs/docs/server/05a-validation.md`).
+
+## Generated CRUD / views (relations-plugin)
+
+- The plugin registers **views, actions, events, and triggers** automatically from `entity`, `itemOf`, `propertyOf`, `*Any`, `relatedTo`, `boundTo`, and `saveAuthor` (see `live-change-stack/framework/relations-plugin/src/index.ts`).
+- **Do not** define a manual `definition.view` / `action` / `event` / `trigger` with the **same name** as a generated one (e.g. `entity` on model `Auction` already creates view **`auction`**).
+- Use **`describe`** before adding custom surface API: `fnm exec -- node server/start.js describe --service myService --output yaml`.
+- Technical inventory: **`docs/docs/server/09-00-relations-generated-artifacts.md`** (built docs path `/server/09-00-relations-generated-artifacts.html`).
+
+## Owner selection — `userItem`, `entity`, domain relations
+
+- **Per logged-in user** (“my X”, owner = `client.user`): use **`userItem`** (or **`userProperty`** for one row per user) with **`use: [ userService, … ]`**. Do **not** hand-declare **`user`** or **`owner`** — user-service injects **`user`** + **`byUser`**. Configure access with **`userReadAccess`**, **`userCreateAccess`**, **`userUpdateAccess`**, **`userDeleteAccess`**, **`userWriteAccess`** (see `live-change-stack/services/user-service/userItem.js`).
+- **Session or User** (guest drafts → sign-in transfer): **`sessionOrUserItem`** / **`sessionOrUserProperty`**. There is no **`sessionItem`** annotation.
+- **Global / role-scoped** catalog entities without a natural “this row belongs to client.user”: often **`entity`**.
+- **Child of a domain parent model** (invoice lines, comments, …): **`itemOf`** / **`propertyOf`** / `*Any`.
+- Typical **`userItem`** API names: **`myUser` + plural(Model)** (range), **`createMyUser` + Model**, **`updateMyUser` + Model**. Relations-plugin may also expose **`create` + Model** from underlying **`itemOf`** — prefer **`createMyUser*`** for consistent **`user`** stamping.
+- Full guide: **`docs/docs/server/09-07-owner-selection-useritem.md`**.
+
 ## Step 2b – Relation arity rules (critical)
 
 Treat arity on two levels:
@@ -86,13 +114,13 @@ Guardrail:
 ### `userItem`
 
 1. Add a `userItem` block inside the model definition.
-2. Set roles for read/write and list which fields can be written.
+2. Set **`userReadAccess`**, **`userCreateAccess`**, **`userUpdateAccess`**, **`userDeleteAccess`**, or **`userWriteAccess`** (see `live-change-stack/services/user-service/userItem.js`). Do **not** declare **`user`** in `properties`.
 
 ```js
 userItem: {
-  readAccessControl: { roles: ['owner', 'admin'] },
-  writeAccessControl: { roles: ['owner', 'admin'] },
-  writeableProperties: ['name']
+  userReadAccess: (params, context) => !!context.client?.user,
+  userWriteAccess: (params, context) => !!context.client?.user,
+  writableProperties: ['name']
 }
 ```
 

package/.claude/skills/live-change-frontend-editor-form/SKILL.md

@@ -51,9 +51,30 @@ identifiers: {} // creates a new record
 
 This is the simplest and most readable approach. Use it when identifiers are available at setup time (static values, route params).
 
+### `crudSource`, `ownerCrud`, and `allowReadWithoutIdentifiers`
+
+Models from **user-service** relations (`userProperty`, `userItem`, `sessionOrUserProperty`, `sessionOrUserItem`, …) expose a second CRUD map on the model: **`ownerCrud`** (see `describe`: `read` is usually **`my…`**, actions are **`setMy…` / `updateMy…` / `setOrUpdateMy…`**). Use:
+
+```javascript
+const editor = await editorData({
+  service: 'userIdentification',
+  model: 'Identification',
+  crudSource: 'ownerCrud',
+  identifiers: {},
+  allowReadWithoutIdentifiers: true,
+  draft: true,
+})
+```
+
+**`allowReadWithoutIdentifiers`** (default `false`): when `true`, `editorData` still subscribes to the **read** view even if `identifiers` is `{}`. Use only when the read view is defined for the current client with no path params (typical `ownerCrud.read`). Keep `false` for normal **`crud.read`** that needs real ids — otherwise you risk unnecessary not-authorized / missing errors.
+
+For **`crud`** (default `crudSource: 'crud'`) with a global read view, pass real **`identifiers`** as before.
+
 ## Step 2 – Build the template with AutoField
 
-Use `editor.model.properties.*` as definitions and `editor.data.value` for v-model bindings:
+Use `editor.model.properties.*` as definitions and `editor.data.value` for v-model bindings.
+
+**Model `if` on properties:** When a property uses `definition.if` (visibility depends on other fields, e.g. `props.portalRole === 'employee'`), pass **`:root-value="editor.data.value"`** on every `AutoField` that relies on that definition. The default `rootValue` is `{}`, so the predicate never sees sibling fields and `if`-gated fields stay hidden. Same rule as `AutoEditor`’s `rootValue` / `ModelEditor`’s `auto-editor` wiring.
 
 **Important:** Always wrap in a `<form>` element. `EditorButtons` uses `type="submit"` / `type="reset"` internally — without a parent `<form>`, the buttons do nothing.
 
@@ -62,12 +83,14 @@ Use `editor.model.properties.*` as definitions and `editor.data.value` for v-mod
   <form @submit.prevent="editor.save()" @reset.prevent="editor.reset()">
     <div class="space-y-4">
       <AutoField
+        :root-value="editor.data.value"
         :definition="editor.model.properties.title"
         v-model="editor.data.value.title"
         :error="editor.propertiesErrors?.title"
         label="Title"
       />
       <AutoField
+        :root-value="editor.data.value"
         :definition="editor.model.properties.body"
         v-model="editor.data.value.body"
         :error="editor.propertiesErrors?.body"
@@ -76,6 +99,7 @@ Use `editor.model.properties.*` as definitions and `editor.data.value` for v-mod
 
       <!-- Custom input inside AutoField — gets label + error automatically -->
       <AutoField
+        :root-value="editor.data.value"
         :definition="editor.model.properties.category"
         v-model="editor.data.value.category"
         :error="editor.propertiesErrors?.category"

package/.cursor/rules/live-change-backend-actions-views-triggers.mdc

@@ -15,6 +15,12 @@ alwaysApply: false
   - używać indeksów zamiast pełnych skanów,
   - zwracać sensowny wynik (ID obiektu, fragment stanu itp.).
 
+### Walidacja i `if`
+
+- Traktuj `if` na property jako warunek widoczności i walidacji.
+- Backendowe auto-validation pomija walidatory pól, dla których `if` zwraca `false`.
+- Dla warunkowego required trzymaj walidatory na polu i modeluj warunek przez `if`, zamiast ręcznie dublować guardy w wielu akcjach.
+
 ### Wzorzec prostej akcji
 
 ```js

package/.cursor/rules/live-change-backend-models-and-relations.mdc

@@ -36,6 +36,30 @@ properties: {
 }
 ```
 
+## Walidacja (`validation` / `softValidation`)
+
+- Używaj **tylko nazw walidatorów**, które istnieją w frameworku albo zostały zarejestrowane w serwisie — pełna lista i przykłady: dokumentacja **Property validation** (`live-change-stack/docs/docs/server/05a-validation.md`, po zbudowaniu docs: `/server/05a-validation.html`).
+- Wbudowane m.in.: `nonEmpty`, `minLength`, `maxLength`, `number`, `integer`, **`min`** / **`max`** z obiektem `{ name: 'min', value: 0 }` (granica liczbowa; często łańcuch `['number', { name: 'min', value: 0 }]`).
+- Własny walidator w serwisie: `definition.validator('email', fabryka)` (np. wzorzec z `email-service` / `password-authentication-service`). Nazwy są kopiowane między serwisami przy starcie — unikaj kolizji (pierwsza rejestracja wygrywa).
+- Na froncie dopnij ten sam klucz na `api.validators` (np. import `clientEmailValidator.js` i `api.validators.email = emailValidator` w `App.vue`), żeby `validateData` / auto-form znały reguły po stronie klienta.
+
+## Relations plugin — co jest generowane (kolizje nazw)
+
+- `@live-change/relations-plugin` sam rejestruje **widoki, akcje, eventy i triggery** według wzorców z `live-change-stack/framework/relations-plugin/src/` (kolejność procesorów: `entity` → `propertyOf`/`itemOf` → … → `saveAuthor`).
+- **Nie** dodawaj ręcznie `definition.view` / `action` / `event` / `trigger` o nazwie już zajętej przez generator (np. model `Auction` z `entity` ma już widok **`auction`** — duplikat kończy się błędem `view auction already exists`).
+- Przed własną rejestracją: `fnm exec -- node server/start.js describe --service … --output yaml`.
+- Inwentarz techniczny: `live-change-stack/docs/docs/server/09-00-relations-generated-artifacts.md` (po buildzie docs: `/server/09-00-relations-generated-artifacts.html`).
+
+## Wybór właściciela — `userItem` vs `entity` vs relacje domenowe
+
+- Lista „moich” rzeczy dla **zalogowanego User** (tworzenie/edycja pod **`client.user`**) → **`userItem`** lub **`userProperty`** + **`use: [ userService, … ]`**. **Nie** dodawaj ręcznego pola **`user`** ani **`owner`** — dodaje je procesor (`live-change-stack/services/user-service/userItem.js`). Dostęp ustawiaj przez **`userReadAccess`**, **`userCreateAccess`**, **`userUpdateAccess`**, **`userDeleteAccess`**, **`userWriteAccess`** — nie wymyślaj nazwy „ownerAccessControl”.
+- Owner **Session lub User** (draft przed loginem → transfer) → **`sessionOrUserItem`** / **`sessionOrUserProperty`** (09-04). Nie ma adnotacji **`sessionItem`**.
+- Encja **globalna** / dostęp głównie po **rolach**, bez naturalnego „ten rekord = ten user” → często **`entity`** (05-models).
+- Dziecko **konkretnego modelu domenowego** (nie „User jako kontener konta”) → **`itemOf`** / **`propertyOf`** / `*Any` (09-01 / 09-02).
+- Wygenerowane nazwy dla **`userItem`** (np. `myUserAuctions`, `createMyUserAuction`): patrz **`09-07-owner-selection-useritem.md`** w docs serwera.
+
+Procesory **user-service** (m.in. `userProperty`, `userItem`, `sessionOrUserProperty`, `sessionOrUserItem`) ustawiają na modelu mapę **`ownerCrud`** obok ewentualnego globalnego **`crud`** — w `describe` widać oba bloki. Na froncie formularze „moje” buduje się przez **`editorData({ crudSource: 'ownerCrud', … })`**; gdy widok **`my…`** nie bierze parametrów ścieżki, często **`identifiers: {}`** + **`allowReadWithoutIdentifiers: true`**. Szczegóły: `live-change-stack/docs/docs/frontend/09-api-frontend-auto-form.md`.
+
 ## Arity relacji (bardzo ważne)
 
 Rozróżniaj dwa poziomy:
@@ -61,7 +85,7 @@ Przykłady:
 
 ## `userItem` – zasób należący do użytkownika
 
-Używaj, gdy model należy do zalogowanego użytkownika.
+Używaj, gdy model należy do zalogowanego użytkownika (preferuj **userItem** zamiast **`entity`** + ręcznego **`owner`** dla typowych list „moich” obiektów — szczegóły: `docs/docs/server/09-07-owner-selection-useritem.md`).
 
 ```js
 definition.model({

package/.cursor/rules/live-change-frontend-vue-primevue.mdc

@@ -66,6 +66,10 @@ Schemat decyzji:
 2. Edytuje rekord modelu (create/update)? → **Tak**: użyj `editorData`. **Nie**: użyj `actionData`.
 3. `<command-form>` tylko do najprostszych jednorazowych przypadków.
 
+**`editorData` — `crud` vs `ownerCrud`:** domyślnie używane jest `model.crud`. Modele z relacji user-service mają często też **`model.ownerCrud`** (`describe`): wtedy `editorData({ crudSource: 'ownerCrud', … })`. Gdy widok read typu **`my…`** nie ma parametrów w ścieżce, a przekazujesz `identifiers: {}`, ustaw **`allowReadWithoutIdentifiers: true`** (inaczej `editorData` nie podłączy `live` zapisanej wartości). Szczegóły: `live-change-stack/docs/docs/frontend/09-api-frontend-auto-form.md`.
+
+**`AutoField` i `definition.if`:** pola z warunkiem `if` w definicji modelu oceniają widoczność względem obiektu przekazanego jako **`rootValue`**. Bez **`:root-value="editor.data.value"`** (lub równoważnego całego rekordu) domyślne `{}` ukrywa te pola mimo poprawnego `v-model`.
+
 ## Autosave helpery – `synchronized` i `synchronizedList`
 
 Używaj helperów dla danych z `live(...)`:

package/.cursor/skills/live-change-design-actions-views-triggers.md

@@ -35,6 +35,12 @@ Use this skill to design **actions, views, and triggers** in LiveChange services
    - session keys,
    - any data needed for the next step.
 
+### Validation and `if`
+
+- Define conditional fields with property-level `if` directly on the schema field.
+- Runtime validation skips fields where `if` evaluates to `false` (frontend `validateData` and backend auto-validation).
+- Keep the validator list (`validation`, `softValidation`) on the field itself, and avoid duplicating the same condition in ad-hoc `execute` guards unless business logic requires additional checks.
+
 Example:
 
 ```js

package/Dockerfile

@@ -1,4 +1,4 @@
-FROM --platform=amd64 debian:buster
+FROM --platform=amd64 debian:bookworm
 
 # SYSTEM
 RUN echo no cache 3
@@ -21,6 +21,8 @@ RUN apt-get install -y nodejs
 #NPM, PM2
 RUN npm install cross-env yarn typescript -g
 
+RUN echo no cache 1
+
 # APP
 RUN mkdir -p /app
 WORKDIR /app
@@ -49,4 +51,4 @@ COPY docker/start-service.sh /start-service.sh
 COPY docker/app.initd.sh /etc/init.d/app
 
 #CMD /start-service.sh
-CMD node --inspect=0.0.0.0:9229 --max-old-space-size=512 dist/server/start.js ssrServer --withApi --withServices --updateServices --enableSessions --createDb
+CMD node --inspect=0.0.0.0:9229 --expose_gc dist/server/start.js ssrServer --withApi --withServices --updateServices --enableSessions --createDb

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@live-change/frontend-template",
-  "version": "0.9.206",
+  "version": "0.9.207",
   "scripts": {
     "memDev": "tsx --inspect --expose-gc server/start.js memDev --enableSessions --initScript ./init.js --dbAccess",
     "localDevInit": "tsx server/start.js localDev --enableSessions --initScript ./init.js --dbAccess",
@@ -48,57 +48,57 @@
     "@codemirror/language": "6.12.3",
     "@dotenvx/dotenvx": "0.27.0",
     "@fortawesome/fontawesome-free": "^6.7.2",
-    "@live-change/access-control-frontend": "^0.9.206",
-    "@live-change/access-control-service": "^0.9.206",
-    "@live-change/agreement-service": "^0.9.206",
-    "@live-change/backup-service": "^0.9.206",
-    "@live-change/blog-frontend": "^0.9.206",
-    "@live-change/blog-service": "^0.9.206",
-    "@live-change/cli": "^0.9.206",
-    "@live-change/content-frontend": "^0.9.206",
-    "@live-change/content-service": "^0.9.206",
-    "@live-change/cron-service": "^0.9.206",
-    "@live-change/dao": "^0.9.206",
-    "@live-change/dao-vue3": "^0.9.206",
-    "@live-change/dao-websocket": "^0.9.206",
-    "@live-change/db-client": "^0.9.206",
-    "@live-change/draft-service": "^0.9.206",
-    "@live-change/e2e-test": "^0.9.206",
-    "@live-change/email-service": "^0.9.206",
-    "@live-change/framework": "^0.9.206",
-    "@live-change/frontend-auto-form": "^0.9.206",
-    "@live-change/frontend-base": "^0.9.206",
-    "@live-change/geoip-service": "^0.9.206",
-    "@live-change/google-authentication-service": "^0.9.206",
-    "@live-change/image-frontend": "^0.9.206",
-    "@live-change/linkedin-authentication-service": "^0.9.206",
-    "@live-change/locale-settings-service": "^0.9.206",
-    "@live-change/notification-service": "^0.9.206",
-    "@live-change/password-authentication-service": "^0.9.206",
-    "@live-change/peer-connection-frontend": "^0.9.206",
-    "@live-change/peer-connection-service": "^0.9.206",
-    "@live-change/prosemirror-service": "^0.9.206",
-    "@live-change/scope-service": "^0.9.206",
-    "@live-change/secret-code-service": "^0.9.206",
-    "@live-change/secret-link-service": "^0.9.206",
-    "@live-change/security-service": "^0.9.206",
-    "@live-change/session-service": "^0.9.206",
-    "@live-change/task-frontend": "^0.9.206",
-    "@live-change/task-service": "^0.9.206",
-    "@live-change/timer-service": "^0.9.206",
-    "@live-change/upload-frontend": "^0.9.206",
-    "@live-change/upload-service": "^0.9.206",
-    "@live-change/url-frontend": "^0.9.206",
-    "@live-change/url-service": "^0.9.206",
-    "@live-change/user-frontend": "^0.9.206",
-    "@live-change/user-identification-service": "^0.9.206",
-    "@live-change/user-service": "^0.9.206",
-    "@live-change/video-call-frontend": "^0.9.206",
-    "@live-change/video-call-service": "^0.9.206",
-    "@live-change/vote-service": "^0.9.206",
-    "@live-change/vue3-components": "^0.9.206",
-    "@live-change/vue3-ssr": "^0.9.206",
-    "@live-change/wysiwyg-frontend": "^0.9.206",
+    "@live-change/access-control-frontend": "^0.9.207",
+    "@live-change/access-control-service": "^0.9.207",
+    "@live-change/agreement-service": "^0.9.207",
+    "@live-change/backup-service": "^0.9.207",
+    "@live-change/blog-frontend": "^0.9.207",
+    "@live-change/blog-service": "^0.9.207",
+    "@live-change/cli": "^0.9.207",
+    "@live-change/content-frontend": "^0.9.207",
+    "@live-change/content-service": "^0.9.207",
+    "@live-change/cron-service": "^0.9.207",
+    "@live-change/dao": "^0.9.207",
+    "@live-change/dao-vue3": "^0.9.207",
+    "@live-change/dao-websocket": "^0.9.207",
+    "@live-change/db-client": "^0.9.207",
+    "@live-change/draft-service": "^0.9.207",
+    "@live-change/e2e-test": "^0.9.207",
+    "@live-change/email-service": "^0.9.207",
+    "@live-change/framework": "^0.9.207",
+    "@live-change/frontend-auto-form": "^0.9.207",
+    "@live-change/frontend-base": "^0.9.207",
+    "@live-change/geoip-service": "^0.9.207",
+    "@live-change/google-authentication-service": "^0.9.207",
+    "@live-change/image-frontend": "^0.9.207",
+    "@live-change/linkedin-authentication-service": "^0.9.207",
+    "@live-change/locale-settings-service": "^0.9.207",
+    "@live-change/notification-service": "^0.9.207",
+    "@live-change/password-authentication-service": "^0.9.207",
+    "@live-change/peer-connection-frontend": "^0.9.207",
+    "@live-change/peer-connection-service": "^0.9.207",
+    "@live-change/prosemirror-service": "^0.9.207",
+    "@live-change/scope-service": "^0.9.207",
+    "@live-change/secret-code-service": "^0.9.207",
+    "@live-change/secret-link-service": "^0.9.207",
+    "@live-change/security-service": "^0.9.207",
+    "@live-change/session-service": "^0.9.207",
+    "@live-change/task-frontend": "^0.9.207",
+    "@live-change/task-service": "^0.9.207",
+    "@live-change/timer-service": "^0.9.207",
+    "@live-change/upload-frontend": "^0.9.207",
+    "@live-change/upload-service": "^0.9.207",
+    "@live-change/url-frontend": "^0.9.207",
+    "@live-change/url-service": "^0.9.207",
+    "@live-change/user-frontend": "^0.9.207",
+    "@live-change/user-identification-service": "^0.9.207",
+    "@live-change/user-service": "^0.9.207",
+    "@live-change/video-call-frontend": "^0.9.207",
+    "@live-change/video-call-service": "^0.9.207",
+    "@live-change/vote-service": "^0.9.207",
+    "@live-change/vue3-components": "^0.9.207",
+    "@live-change/vue3-ssr": "^0.9.207",
+    "@live-change/wysiwyg-frontend": "^0.9.207",
     "@vueuse/core": "^12.3.0",
     "codeceptjs-assert": "^0.0.5",
     "compression": "^1.7.5",
@@ -122,7 +122,7 @@
   "devDependencies": {
     "copyfiles": "^2.4.1",
     "generate-password": "^1.7.1",
-    "playwright": "^1.49.1",
+    "playwright": "=1.50.1",
     "random-profile-generator": "^2.3.0",
     "tsx": "^4.21.0",
     "txtgen": "^3.0.7",
@@ -131,5 +131,5 @@
   "author": "Michał Łaszczewski <michal@laszczewski.pl>",
   "license": "ISC",
   "description": "",
-  "gitHead": "550ec614c03ed33fbb8a094d23a63dd2d20d5de3"
+  "gitHead": "1937f8f9798d5df011b38341119a25afe0def6d1"
 }