@chill-sharp/create-app 1.1.12 → 1.1.15

package/README.md

@@ -1,12 +1,12 @@
-# Create ChillSharp App
-
-Creates a ready-to-run Angular application shell backed by the published ChillSharp npm packages.
-
-```bash
-npm create @chill-sharp/app my-app
-cd my-app
-npm install
-npm start
-```
-
-The generator copies the client-owned application shell and configures it to use `@chill-sharp/ts-client`, `@chill-sharp/ng-client`, and `@chill-sharp/ui-core` from npm.
+# Create ChillSharp App
+
+Creates a ready-to-run Angular application shell backed by the published ChillSharp npm packages.
+
+```bash
+npm create @chill-sharp/app my-app
+cd my-app
+npm install
+npm start
+```
+
+The generator copies the client-owned application shell and configures it to use `@chill-sharp/ts-client`, `@chill-sharp/ng-client`, and `@chill-sharp/ui-core` from npm.

package/package.json

@@ -1,36 +1,36 @@
-{
-  "name": "@chill-sharp/create-app",
-  "repository": {
-    "type": "git",
-    "url": "git+https://github.com/e-500/chill-sharp.git",
-    "directory": "extra/chill-sharp-create-app"
-  },
-  "version": "1.1.12",
-  "description": "Create an Angular application powered by ChillSharp UI.",
-  "license": "AGPL-3.0-or-later",
-  "type": "module",
-  "bin": {
-    "create-chill-sharp-app": "./bin/create-chill-sharp-app.mjs"
-  },
-  "scripts": {
-    "build": "node --check bin/create-chill-sharp-app.mjs"
-  },
-  "files": [
-    "bin",
-    "template",
-    "README.md"
-  ],
-  "engines": {
-    "node": ">=20"
-  },
-  "keywords": [
-    "chillsharp",
-    "angular",
-    "starter",
-    "generator"
-  ],
-  "author": "Andrea Piovesan",
-  "publishConfig": {
-    "access": "public"
-  }
-}
+{
+  "name": "@chill-sharp/create-app",
+  "repository": {
+    "type": "git",
+    "url": "git+https://github.com/e-500/chill-sharp.git",
+    "directory": "extra/chill-sharp-create-app"
+  },
+  "version": "1.1.15",
+  "description": "Create an Angular application powered by ChillSharp UI.",
+  "license": "AGPL-3.0-or-later",
+  "type": "module",
+  "bin": {
+    "create-chill-sharp-app": "./bin/create-chill-sharp-app.mjs"
+  },
+  "scripts": {
+    "build": "node --check bin/create-chill-sharp-app.mjs"
+  },
+  "files": [
+    "bin",
+    "template",
+    "README.md"
+  ],
+  "engines": {
+    "node": ">=20"
+  },
+  "keywords": [
+    "chillsharp",
+    "angular",
+    "starter",
+    "generator"
+  ],
+  "author": "Andrea Piovesan",
+  "publishConfig": {
+    "access": "public"
+  }
+}

package/template/.agents/skills/chillsharp-current-user-preferences/SKILL.md

@@ -1,70 +1,70 @@
----
-name: chillsharp-current-user-preferences
-description: Configure, expose, and consume ChillSharp.Auth's cached current-user culture, time zone, date-format, number-format, and theme preferences in server logic and UI clients.
----
-
-# ChillSharp Current User Preferences
-
-Use this skill when a ChillSharp feature needs the authenticated user's display culture, time zone, date format, or number format. It covers server-side lifecycle hooks and UI/client consumption of the authoritative `AuthUser` preferences. Do not use it for browser-only preferences unrelated to `AuthUser`.
-
-## Model
-
-`ChillUserPreferences` is an immutable snapshot with `DisplayCultureName`, `DisplayTimeZone`, `DisplayDateFormat`, `DisplayNumberFormat`, and `PreferredTheme`. The backend stores `PreferredTheme` as an opaque string. In UI Core, unauthenticated users follow browser `prefers-color-scheme`; clients register extra themes with `provideChillSharpUiCore({ additionalThemes: ['theme-name'] })`. Entity hooks read the snapshot synchronously through:
-
-```csharp
-var preferences = context.GetCurrentUserPreferences();
-```
-
-Never load `AuthUser` from an `OnCreate`, `OnUpdate`, or other lifecycle hook merely to obtain these values.
-
-## Auth integration
-
-`AddChillAuthApi` registers `IChillAuthUserPreferencesAccessor` and the singleton `IChillAuthUserPreferencesCache`. Login and token refresh warm the snapshot; `ChillAuthService` refreshes it after an `AuthUser` save and removes it for deleted or renamed external identities.
-
-For a custom host DbContext, inject the scoped accessor and implement the two `IChillContext` methods below. Keep the accessor optional only when the context must also be constructible outside DI, such as for migrations or tests.
-
-```csharp
-private readonly IChillAuthUserPreferencesAccessor? _userPreferencesAccessor;
-
-public ChillUserPreferences GetCurrentUserPreferences() =>
-    _userPreferencesAccessor?.Current ?? ChillUserPreferences.Empty;
-
-public string GetDefaultUserCultureName()
-{
-    var cultureName = GetCurrentUserPreferences().DisplayCultureName;
-    return string.IsNullOrWhiteSpace(cultureName) ? GetPrimaryCultureName() : cultureName;
-}
-```
-
-The accessor is cache-only: when there is no authenticated principal or no warmed snapshot, it returns `ChillUserPreferences.Empty`. Do not add a fallback database query to lifecycle hooks.
-
-## API and client use
-
-The authenticated endpoint `GET /api/chill-auth/current-user-preferences` returns the same `ChillUserPreferences` snapshot as JSON:
-
-```json
-{
-  "displayCultureName": "it-IT",
-  "displayTimeZone": "Europe/Rome",
-  "displayDateFormat": "dd/MM/yyyy",
-  "displayNumberFormat": "N2"
-}
-```
-
-Use this endpoint after authentication and when restoring a session; do not infer the active display culture or time zone from the browser, operating system, token claims, or auth-management user endpoints. The C#, Python, TypeScript, Angular, Vue, and React clients expose it as `GetCurrentUserPreferences`, `get_current_user_preferences`, or `getCurrentUserPreferences`; the Vue and React packages also provide `useCurrentUserPreferences`.
-
-In Angular UI Core, inject `ChillService` and read its `userPreferences` signal (or its `displayCultureName`, `displayTimeZone`, `displayDateFormat`, and `displayNumberFormat` projections). Use these values to select UI language, format and parse dates and numbers, and convert UTC timestamps. Treat all fields as optional and choose an explicit fallback only when needed.
-
-## Entity use
-
-Use `DisplayTimeZone` as an IANA zone identifier only after validating it with the application's time-zone policy. Treat all fields as optional and provide an explicit fallback where one is required.
-
-```csharp
-public override void OnUpdate(IChillContext context)
-{
-    var timeZone = context.GetCurrentUserPreferences().DisplayTimeZone;
-    // Apply application-specific behavior only when timeZone is available.
-}
-```
-
-For full setup and cache behavior, read [CurrentUserPreferences.md](../../../doc/CurrentUserPreferences.md).
+---
+name: chillsharp-current-user-preferences
+description: Configure, expose, and consume ChillSharp.Auth's cached current-user culture, time zone, date-format, number-format, and theme preferences in server logic and UI clients.
+---
+
+# ChillSharp Current User Preferences
+
+Use this skill when a ChillSharp feature needs the authenticated user's display culture, time zone, date format, or number format. It covers server-side lifecycle hooks and UI/client consumption of the authoritative `AuthUser` preferences. Do not use it for browser-only preferences unrelated to `AuthUser`.
+
+## Model
+
+`ChillUserPreferences` is an immutable snapshot with `DisplayCultureName`, `DisplayTimeZone`, `DisplayDateFormat`, `DisplayNumberFormat`, and `PreferredTheme`. The backend stores `PreferredTheme` as an opaque string. In UI Core, unauthenticated users follow browser `prefers-color-scheme`; clients register extra themes with `provideChillSharpUiCore({ additionalThemes: ['theme-name'] })`. Entity hooks read the snapshot synchronously through:
+
+```csharp
+var preferences = context.GetCurrentUserPreferences();
+```
+
+Never load `AuthUser` from an `OnCreate`, `OnUpdate`, or other lifecycle hook merely to obtain these values.
+
+## Auth integration
+
+`AddChillAuthApi` registers `IChillAuthUserPreferencesAccessor` and the singleton `IChillAuthUserPreferencesCache`. Login and token refresh warm the snapshot; `ChillAuthService` refreshes it after an `AuthUser` save and removes it for deleted or renamed external identities.
+
+For a custom host DbContext, inject the scoped accessor and implement the two `IChillContext` methods below. Keep the accessor optional only when the context must also be constructible outside DI, such as for migrations or tests.
+
+```csharp
+private readonly IChillAuthUserPreferencesAccessor? _userPreferencesAccessor;
+
+public ChillUserPreferences GetCurrentUserPreferences() =>
+    _userPreferencesAccessor?.Current ?? ChillUserPreferences.Empty;
+
+public string GetDefaultUserCultureName()
+{
+    var cultureName = GetCurrentUserPreferences().DisplayCultureName;
+    return string.IsNullOrWhiteSpace(cultureName) ? GetPrimaryCultureName() : cultureName;
+}
+```
+
+The accessor is cache-only: when there is no authenticated principal or no warmed snapshot, it returns `ChillUserPreferences.Empty`. Do not add a fallback database query to lifecycle hooks.
+
+## API and client use
+
+The authenticated endpoint `GET /api/chill-auth/current-user-preferences` returns the same `ChillUserPreferences` snapshot as JSON:
+
+```json
+{
+  "displayCultureName": "it-IT",
+  "displayTimeZone": "Europe/Rome",
+  "displayDateFormat": "dd/MM/yyyy",
+  "displayNumberFormat": "N2"
+}
+```
+
+Use this endpoint after authentication and when restoring a session; do not infer the active display culture or time zone from the browser, operating system, token claims, or auth-management user endpoints. The C#, Python, TypeScript, Angular, Vue, and React clients expose it as `GetCurrentUserPreferences`, `get_current_user_preferences`, or `getCurrentUserPreferences`; the Vue and React packages also provide `useCurrentUserPreferences`.
+
+In Angular UI Core, inject `ChillService` and read its `userPreferences` signal (or its `displayCultureName`, `displayTimeZone`, `displayDateFormat`, and `displayNumberFormat` projections). Use these values to select UI language, format and parse dates and numbers, and convert UTC timestamps. Treat all fields as optional and choose an explicit fallback only when needed.
+
+## Entity use
+
+Use `DisplayTimeZone` as an IANA zone identifier only after validating it with the application's time-zone policy. Treat all fields as optional and provide an explicit fallback where one is required.
+
+```csharp
+public override void OnUpdate(IChillContext context)
+{
+    var timeZone = context.GetCurrentUserPreferences().DisplayTimeZone;
+    // Apply application-specific behavior only when timeZone is available.
+}
+```
+
+For full setup and cache behavior, read [CurrentUserPreferences.md](../../../doc/CurrentUserPreferences.md).

package/template/.agents/skills/chillsharp-ui-template/SKILL.md

@@ -1,18 +1,18 @@
----
-name: chillsharp-ui-template
-description: Build and customize Angular ChillSharp client projects from the UI template, including plugins, overrides, i18n, permissions, and runtime configuration.
----
-
-# ChillSharp UI Client Template
-
-Use this skill for work in `chill-sharp-ui-template` or a client repository created from it.
-
-The template owns runtime configuration, branding, routes, client plugins, and overrides. Shared controls, data access, schema rendering, auth, i18n primitives, and permission evaluation belong in `@chill-sharp/ui-core` and the ChillSharp client packages. Do not copy or patch shared package internals.
-
-Keep `provideClientTemplateProviders()` in the app provider chain. Register feature routes in `src/app/core/plugins/register-client-plugins.ts`; register deliberate provider replacements in `src/app/core/overrides/register-client-overrides.ts`. Use public package APIs only.
-
-Treat backend schema as the source of entity/property metadata rather than duplicating it in Angular. Use runtime API configuration from `public/env.js`. Request localized text with an explicit culture and preserve backend fallback behavior. UI permission checks can hide or disable operations, but the protected backend is the enforcement boundary.
-
-Permission-sensitive features must account for `Module -> Entity -> Property`: entity `Query/Create/Update/Delete` is separate from property `See/Modify`. Never infer write access from a visible field.
-
-Add plugins under the client-owned plugin folder, register providers through the override/provider points, keep tenant/feature flags/branding in runtime config, add focused tests, and run `npm run build` after registration changes. This `.agents/skills` directory travels with the template into client repositories.
+---
+name: chillsharp-ui-template
+description: Build and customize Angular ChillSharp client projects from the UI template, including plugins, overrides, i18n, permissions, and runtime configuration.
+---
+
+# ChillSharp UI Client Template
+
+Use this skill for work in `chill-sharp-ui-template` or a client repository created from it.
+
+The template owns runtime configuration, branding, routes, client plugins, and overrides. Shared controls, data access, schema rendering, auth, i18n primitives, and permission evaluation belong in `@chill-sharp/ui-core` and the ChillSharp client packages. Do not copy or patch shared package internals.
+
+Keep `provideClientTemplateProviders()` in the app provider chain. Register feature routes in `src/app/core/plugins/register-client-plugins.ts`; register deliberate provider replacements in `src/app/core/overrides/register-client-overrides.ts`. Use public package APIs only.
+
+Treat backend schema as the source of entity/property metadata rather than duplicating it in Angular. Use runtime API configuration from `public/env.js`. Request localized text with an explicit culture and preserve backend fallback behavior. UI permission checks can hide or disable operations, but the protected backend is the enforcement boundary.
+
+Permission-sensitive features must account for `Module -> Entity -> Property`: entity `Query/Create/Update/Delete` is separate from property `See/Modify`. Never infer write access from a visible field.
+
+Add plugins under the client-owned plugin folder, register providers through the override/provider points, keep tenant/feature flags/branding in runtime config, add focused tests, and run `npm run build` after registration changes. This `.agents/skills` directory travels with the template into client repositories.

package/template/.editorconfig

@@ -1,11 +1,11 @@
-root = true
-
-[*.{ts,js,json,md,scss,html}]
-charset = utf-8
-indent_style = space
-indent_size = 2
-insert_final_newline = true
-trim_trailing_whitespace = true
-
-[*.md]
-trim_trailing_whitespace = false
+root = true
+
+[*.{ts,js,json,md,scss,html}]
+charset = utf-8
+indent_style = space
+indent_size = 2
+insert_final_newline = true
+trim_trailing_whitespace = true
+
+[*.md]
+trim_trailing_whitespace = false

package/template/.github/workflows/ci.yml

@@ -1,33 +1,33 @@
-name: CI
-
-on:
-  push:
-    branches:
-      - main
-  pull_request:
-
-jobs:
-  build-and-test:
-    runs-on: ubuntu-latest
-
-    steps:
-      - name: Checkout
-        uses: actions/checkout@v4
-
-      - name: Setup Node
-        uses: actions/setup-node@v4
-        with:
-          node-version: 22
-          cache: npm
-
-      - name: Install
-        run: npm ci
-
-      - name: Lint
-        run: npm run lint
-
-      - name: Build
-        run: npm run build
-
-      - name: Test
-        run: npm run test -- --browsers=ChromeHeadless
+name: CI
+
+on:
+  push:
+    branches:
+      - main
+  pull_request:
+
+jobs:
+  build-and-test:
+    runs-on: ubuntu-latest
+
+    steps:
+      - name: Checkout
+        uses: actions/checkout@v4
+
+      - name: Setup Node
+        uses: actions/setup-node@v4
+        with:
+          node-version: 22
+          cache: npm
+
+      - name: Install
+        run: npm ci
+
+      - name: Lint
+        run: npm run lint
+
+      - name: Build
+        run: npm run build
+
+      - name: Test
+        run: npm run test -- --browsers=ChromeHeadless

package/template/.github/workflows/deploy.yml

@@ -1,36 +1,36 @@
-name: Deploy
-
-on:
-  workflow_dispatch:
-  push:
-    tags:
-      - "v*"
-
-jobs:
-  deploy:
-    runs-on: ubuntu-latest
-
-    steps:
-      - name: Checkout
-        uses: actions/checkout@v4
-
-      - name: Setup Node
-        uses: actions/setup-node@v4
-        with:
-          node-version: 22
-          cache: npm
-
-      - name: Install
-        run: npm ci
-
-      - name: Build
-        run: npm run build
-
-      - name: Publish artifact
-        uses: actions/upload-artifact@v4
-        with:
-          name: client-ui-build
-          path: dist/chill-sharp-ui-template
-
-      - name: Deploy placeholder
-        run: echo "Replace this step with the target hosting deployment command."
+name: Deploy
+
+on:
+  workflow_dispatch:
+  push:
+    tags:
+      - "v*"
+
+jobs:
+  deploy:
+    runs-on: ubuntu-latest
+
+    steps:
+      - name: Checkout
+        uses: actions/checkout@v4
+
+      - name: Setup Node
+        uses: actions/setup-node@v4
+        with:
+          node-version: 22
+          cache: npm
+
+      - name: Install
+        run: npm ci
+
+      - name: Build
+        run: npm run build
+
+      - name: Publish artifact
+        uses: actions/upload-artifact@v4
+        with:
+          name: client-ui-build
+          path: dist/chill-sharp-ui-template
+
+      - name: Deploy placeholder
+        run: echo "Replace this step with the target hosting deployment command."