kopular 0.5.0 → 0.6.1

package/LLM.md

@@ -1,17 +1,17 @@
 # Kopular — LLM reference
 
 Complete reference for generating correct Kopular code. This is a spec, not a tutorial —
-see `README.md` for narrative/rationale. Kopular is 6 files total; this covers all of
+see `README.md` for narrative/rationale. Kopular is 7 files total; this covers all of
 them. For the host language, see KopScript's own `LLM.md` in the `Kop` repo (or its
 published `LLM.md` on the `kopscript` npm package) — that reference is a prerequisite,
 not repeated here.
 
 Published as npm `kopular`. Entry points: `kopular` / `kopular/component` (Component),
 `kopular/router` (Router), `kopular/dom` (ambient DOM bindings), `kopular/directives`
-(If), `kopular/http` (Http). Also ships a bin, `kp` — `npx kp new <dir>` scaffolds a new
-project (the `extern` bindings below, plus the vendor/serve scripts needed to run in a
-browser) rather than requiring it be reconstructed by hand; prefer it over hand-writing
-the section below for a new project.
+(If), `kopular/http` (Http), `kopular/forms` (FormField, Validators). Also ships a bin,
+`kp` — `npx kp new <dir>` scaffolds a new project (the `extern` bindings below, plus the
+vendor/serve scripts needed to run in a browser) rather than requiring it be reconstructed
+by hand; prefer it over hand-writing the section below for a new project.
 
 ## Consuming Kopular from your own KopScript project
 
@@ -47,8 +47,38 @@ extern class Http {
   static task<Response> Patch(string url, string jsonBody);
   static task<Response> Delete(string url);
 } from "kopular/http";
+
+extern class Validators {
+  static string? Required(string value);
+  static string? MinLength(string value, number min);
+  static string? MaxLength(string value, number max);
+  static string? Email(string value);
+  static string? Min(number value, number min);
+  static string? Max(number value, number max);
+} from "kopular/forms";
+```
+
+**`extern class` has no `<T>` syntax** — `extern class FormField<T> { ... }` is a parse
+error (`ExternClassDecl` has no `typeParam`, unlike a real `ClassDecl`/`InterfaceDecl`).
+Describe one concrete instantiation per `T` you actually need instead, aliasing the same
+real export with `as` (the same trust-based, per-shape approach `Http`'s typed-JSON gap
+above already uses) — e.g. for a `FormField<string>`:
+
+```ks
+extern class StringField {
+  constructor(string initial, (string) => string? validate);
+  state<string> Value;
+  state<string?> Error;
+  state<bool> Touched;
+  void Touch();
+  bool Valid();
+} from "kopular/forms" as "FormField";
 ```
 
+`Value`/`Error`/`Touched` are declared as bare properties (`state<T> Value;`, no
+`{ get; }`) — `extern class` supports a plain field declaration for exactly this case,
+not just get/set accessor pairs.
+
 You also need your own ambient DOM `extern` block (`document`, `Element`, `Event`, ...) —
 Kopular's own copy in `dom.ks` isn't reachable across the package boundary; redeclare the
 handful of members you actually use. See KopularDemo's `src/kopular_bindings.ks` for a
@@ -128,8 +158,23 @@ nav.Navigate("/about");                          // pushState + immediate re-ren
 - `Navigate(path)` calls `history.pushState` then re-renders immediately. A browser
   back/forward triggers re-render via a `popstate` listener registered in the
   constructor — `Navigate()` itself doesn't rely on that event.
-- Needs a server that falls back to the app shell for any unrecognized path (a plain
-  static server has nothing to serve at `/about` on direct load/refresh).
+- **Every deployment target needs its own SPA/history-fallback config — this is
+  unavoidable, not a Kopular gap.** A direct load or refresh at `/about` is a plain HTTP
+  request that reaches your host *before* any JS (Router included) has run, so no
+  client-side router in any language/framework can intercept it; the host itself has to
+  respond with the app shell for any route it doesn't have a literal file for. Configure
+  this on every host you deploy to, not just in local dev:
+  - Local dev (`ks watch` + a static file server): see KopularDemo's `scripts/serve.mjs`
+    — falls back to `index.html` only for an extension-less path, so a genuinely missing
+    `.js`/`.css` still 404s.
+  - Cloudflare Workers (what KopularDemo itself deploys to): `wrangler.jsonc`'s
+    `assets.not_found_handling: "single-page-application"`. Coarser than `serve.mjs` —
+    it falls back for *any* unmatched request, extension or not, so a typo'd asset URL
+    silently serves the app shell instead of 404ing (confirmed via `wrangler dev`; no
+    config short of a custom Worker distinguishes the two cases).
+  - Any other static host (Netlify, Vercel, S3+CloudFront, nginx, ...) has an equivalent
+    "SPA fallback" / "custom 404 → index.html" option — look for that host's own docs on
+    single-page-application routing, the terminology is standard across all of them.
 
 ## `If` (`directives.ks`) — the `*ngIf` equivalent
 
@@ -176,7 +221,8 @@ r.status   // number
 await r.text();   // task<string> — the raw body, nothing more
 ```
 
-**No typed JSON deserialization** — no generics means no safe `Get<T>(url): task<T>`.
+**No typed JSON deserialization** — KopScript's generics are classes/interfaces only (no
+generic functions/methods), so there's no safe `task<T> Get<T>(string url)`.
 Get a typed response by describing its shape as its own `extern class` and parsing with
 a per-shape `extern ... as "JSON.parse"` (unchecked, same trust model as every other
 `extern`):
@@ -194,6 +240,36 @@ hypothetical `Delete`-with-a-body) need one for `{ method, headers, body }`, whi
 KopScript categorically cannot construct — Kopular ships one small hand-written JS
 function (`http_runtime.js`, not compiled from `.ks`) that does, for exactly that reason.
 
+## `FormField<T>` / `Validators` (`forms.ks`)
+
+```ks
+FormField<string> email = new FormField<string>("", (string v) => {
+  string? required = Validators.Required(v);
+  if (required != null) { return required; }
+  return Validators.Email(v);
+});
+
+email.Value.Value = "x";        // state<T> — revalidates automatically on assignment
+email.Error.Value               // string? — current validator's message, or null
+email.Touched.Value             // bool — only true after Touch() (call on blur)
+email.Touch();
+email.Valid();                  // bool — Error.Value == null
+```
+
+`Validators.Required/MinLength/MaxLength/Email` are `(string) => string?`;
+`Validators.Min/Max` are `(number) => string?`. Each returns an error message or `null`.
+
+**No array-of-validators parameter** — KopScript has no array-of-function-values type
+(`((T) => string?)[]` doesn't parse: the parser reads a second `(...)  => ...` immediately
+after the first as a nested function type, not an array element type, and errors expecting
+`=>`). Combine checks as an if-chain in one lambda instead (see the `email` example above)
+— this is the same reason `FormField<T>`'s constructor takes exactly one validator
+function, not a list.
+
+**No DOM binding** — wiring `.Value` to a real `<input>` is a plain `addEventListener`
+call in your own `Render()`, the same as any other event handler; there is no
+`[(ngModel)]`-equivalent.
+
 ## Dependency injection — no container, no decorators
 
 There is no injector, no `@Injectable`, no provider tokens. "Injecting" a service is

package/README.md

@@ -26,9 +26,8 @@ Generating Kopular code with an AI coding assistant? Point it at **[`LLM.md`](./
   class.
 - **`Router`**: real URLs (`/about`, not `#/about`) via the History API
   (`pushState`/`popstate`), with route registration as plain method calls, not a config
-  DSL. Needs a server that falls back to the app shell for unrecognized paths — see
-  [KopularDemo](https://dev.azure.com/koppinator/Koppindependence/_git/KopularDemo)'s
-  `scripts/serve.mjs`.
+  DSL. See "Router, and deploying it" below — every deployment target needs its own
+  SPA-fallback config, not just local dev.
 - **Structural directives, no template DSL**: `*ngIf`/`*ngFor`/`*ngSwitch`'s job — build
   a subtree conditionally, repeat one per item, pick one of several cases — done as plain
   function calls (`If(...)`) and existing KopScript expressions (`array.ForEach(...)`,
@@ -36,6 +35,8 @@ Generating Kopular code with an AI coding assistant? Point it at **[`LLM.md`](./
 - **`Http`**: a thin, static wrapper over the real Fetch API (`Http.Get(url)`,
   `Http.Post(url, jsonBody)`, ...) — no HttpClient injection tokens, no RxJS
   observables/operators. See "HTTP" below.
+- **`FormField<T>`**: a single input's value/error/touched state, built on `state<T>` —
+  no two-way-binding magic, no `FormGroup` config object. See "Forms" below.
 
 ## What's here
 
@@ -48,14 +49,20 @@ Generating Kopular code with an AI coding assistant? Point it at **[`LLM.md`](./
 - `src/http.ks` — `Http`, a thin wrapper over `fetch` (see below). `src/http_runtime.js`
   is its one companion file — the single hand-written (not compiled from `.ks`) file in
   Kopular, and why is explained in its own header comment.
+- `src/forms.ks` — `FormField<T>` and `Validators` (see "Forms" below).
+- `bin/kp.mjs` — the `kp new` scaffolding CLI (see "Starting a new project" below); the
+  one hand-written (not compiled from `.ks`) file besides `http_runtime.js`, for the same
+  reason — filesystem scaffolding isn't a Kopular `Component`.
 
-That's the whole framework — six files. Everything else (a real app built on top of it)
+That's the whole framework — seven files, plus the scaffolding CLI. Everything else (a
+real app built on top of it)
 lives in a separate consumer repo, [KopularDemo](https://dev.azure.com/koppinator/Koppindependence/_git/KopularDemo).
 
 ## Dependency injection: the composition root pattern
 
 Kopular has no injector because KopScript has nothing for one to hook into — no
-decorators, no reflection, no generics for a type-safe `Resolve<T>()`. Instead, the
+decorators, no reflection, and no *generic functions* (KopScript's generics are
+classes/interfaces only — see the Kop repo) for a type-safe `Resolve<T>()`. Instead, the
 whole app's service/page graph gets built exactly once, by hand, in one place: a plain
 class with no `Component` base and no framework code in it at all, sometimes called an
 **app container** or (in the wider DI literature) a **composition root**. Everything
@@ -119,6 +126,41 @@ See [KopularDemo](https://dev.azure.com/koppinator/Koppindependence/_git/Kopular
 `src/app_container.ks` and `src/routed_app.ks` for the real, working version this
 example is drawn from.
 
+## Router, and deploying it
+
+```ks
+Router nav = new Router(new NotFoundPage());   // fallback page required up front — no null route
+nav.AddRoute("/", new HomePage(nav));           // pages built once, kept alive for Router's lifetime
+nav.AddRoute("/about", new AboutPage(nav));
+nav.Mount(document.body);
+nav.Navigate("/about");                          // pushState + immediate re-render
+```
+
+Real URLs via the History API (`pushState`/`popstate`), not `#/about` hash routing.
+`AddRoute` takes an already-constructed `Component`, not a factory, so a page's own
+`state<T>` survives navigating away and back — see "Dependency injection" above for how
+the whole page graph typically gets built once, in a composition root.
+
+**Deploying a Router-based app needs SPA/history-fallback configured on whatever you
+deploy to — this is true of every client-side router in every framework, not a Kopular
+gap.** A direct load or a refresh at `/about` is a plain HTTP request that reaches your
+host before any JS has run, so nothing client-side (Router included) can intercept it;
+the host has to serve the app shell itself for any route it has no literal file for.
+KopularDemo hit exactly this in production (worked when navigated to via a link, 404'd on
+refresh) before its Cloudflare Workers config had this set:
+
+```jsonc
+// wrangler.jsonc
+"assets": {
+  "directory": "./public",
+  "not_found_handling": "single-page-application"
+}
+```
+
+Every static host has an equivalent option (Netlify, Vercel, nginx, ...) — search that
+host's docs for "SPA fallback" or "single-page application routing", the terminology is
+standard. For local dev, see KopularDemo's `scripts/serve.mjs`.
+
 ## Structural directives
 
 Angular's `*ngIf`/`*ngFor`/`*ngSwitch` are template syntax that expands, at compile time,
@@ -209,8 +251,9 @@ anywhere, including straight out of a service's own methods.
 
 **No typed JSON deserialization** — `Response.text()` gets you the raw body, nothing
 more. This isn't a corner cut for v1; it's a direct consequence of two things KopScript
-doesn't have: generics (so there's no safe way to write a general `Get<T>(url):
-task<T>`) and object-literal syntax (`{ ... }` as a value — see below). If you want a
+doesn't have: generic *functions/methods* (KopScript's generics are classes/interfaces
+only, so there's no safe way to write a general `task<T> Get<T>(string url)`) and
+object-literal syntax (`{ ... }` as a value — see below). If you want a
 typed response, describe its shape as its own `extern class` and parse it yourself with
 a per-shape `extern ... as "JSON.parse"` declaration — the same trust-based approach
 `extern` already uses for everything else, not a new mechanism:
@@ -235,6 +278,49 @@ real global). It's the one file in this package not compiled from `.ks` — ever
 else avoids the problem by only wrapping JS APIs that take plain positional arguments
 (see `dom.ks`'s `addEventListener(string, handler)`, never an options-object-taking API).
 
+## Forms
+
+```ks
+using "./forms";
+
+FormField<string> email = new FormField<string>("", (string v) => {
+  string? required = Validators.Required(v);
+  if (required != null) { return required; }
+  return Validators.Email(v);
+});
+
+email.Value.Value = "not-an-email";
+print(email.Error.Value);   // "Must be a valid email"
+print(email.Valid());       // false
+
+emailInput.addEventListener("input", (Event e) => {
+  email.Value.Value = emailInput.textContent;   // revalidates automatically
+});
+emailInput.addEventListener("blur", (Event e) => { email.Touch(); });
+```
+
+`FormField<T>` holds one input's value, error, and touched state as three ordinary
+`state<T>` boxes — `.Value` (the input's current value, revalidating on every
+assignment), `.Error` (`string?`, the current validator's message or `null`), and
+`.Touched` (`bool`, set by calling `.Touch()` — typically on blur, so a fresh field with
+an invalid initial value like an empty required field doesn't show an error before the
+user has typed anything). Subscribe to any of the three from your `Component`'s
+constructor exactly like `Counter`'s own `state<number>`, to re-render when they change.
+
+A validator is a plain `(T) => string?` — `null` means valid, the same convention
+KopScript's own nullable types use elsewhere. **There's no array-of-validators
+constructor parameter** — KopScript has no syntax for an array of function values — so
+combining more than one check (as `email` does above) is just an `if`-chain in one
+lambda, not a combinator API. `Validators` ships the handful of checks almost every form
+needs (`Required`, `MinLength`, `MaxLength`, `Email`, `Min`, `Max`), each returning its
+own message; write your own validator function for anything more specific.
+
+**No two-way data binding** — wiring `Value` to a real `<input>` is the
+`addEventListener` call shown above, the same manual pattern `Counter` already uses for
+its click handler. This is deliberate, not a missing feature: a magic `[(ngModel)]`-style
+binding would be exactly the kind of hidden framework behavior Kopular avoids everywhere
+else.
+
 ## Starting a new project: `kp new`
 
 Everything in the next section — the `extern` bindings, plus a `vendor/kopular/` copy of
@@ -291,6 +377,11 @@ Marking `Render()` `virtual` in the `extern` declaration is what lets a real sub
 for a full working example (components, a service, and routing, all consuming Kopular
 this way).
 
+`extern class` has no `<T>` syntax, so a generic export like `FormField<T>` can't be
+described directly this way — see `LLM.md`'s `FormField<T>`/`Validators` section for the
+per-concrete-type workaround (the same trust-based, per-shape approach the "HTTP" section
+above uses for typed JSON).
+
 ## Getting started (developing Kopular itself)
 
 ```bash

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "kopular",
-  "version": "0.5.0",
+  "version": "0.6.1",
   "description": "Kopular: a small component framework for KopScript — components, reactive state, constructor-injected services, routing, structural directives, and HTTP, with no template DSL and no DI container",
   "type": "module",
   "license": "MIT",
@@ -25,7 +25,8 @@
     "./router": "./src/router.js",
     "./dom": "./src/dom.js",
     "./directives": "./src/directives.js",
-    "./http": "./src/http.js"
+    "./http": "./src/http.js",
+    "./forms": "./src/forms.js"
   },
   "files": [
     "src",
@@ -34,13 +35,13 @@
     "LLM.md"
   ],
   "scripts": {
-    "build": "ks build src/router.ks && ks build src/directives.ks && ks build src/http.ks",
+    "build": "ks build src/router.ks && ks build src/directives.ks && ks build src/http.ks && ks build src/forms.ks",
     "prepublishOnly": "npm run build",
     "test": "vitest run",
     "test:watch": "vitest"
   },
   "devDependencies": {
-    "kopscript": "^0.4.0",
+    "kopscript": "^0.4.1",
     "@types/jsdom": "^30.0.0",
     "@types/node": "^20.14.0",
     "jsdom": "^25.0.1",

package/src/forms.js

@@ -0,0 +1,81 @@
+class __KopState {
+  constructor(value) {
+    this._value = value;
+    this._listeners = [];
+  }
+  get Value() { return this._value; }
+  set Value(v) {
+    this._value = v;
+    for (const listener of this._listeners) listener(v);
+  }
+  Subscribe(listener) {
+    this._listeners.push(listener);
+  }
+}
+
+export class FormField {
+  constructor(initial, validate) {
+    (this.Value = new __KopState(initial));
+    (this.Error = new __KopState(validate(initial)));
+    (this.Touched = new __KopState(false));
+    this.Value.Subscribe((v) => {
+  (this.Error.Value = validate(v));
+});
+  }
+
+  Touch() {
+    (this.Touched.Value = true);
+  }
+
+  Valid() {
+    return (this.Error.Value === null);
+  }
+}
+export class Validators {
+  static Required(value) {
+    if ((value.trim().length === 0)) {
+      return "Required";
+    }
+    return null;
+  }
+
+  static MinLength(value, min) {
+    if ((value.length < min)) {
+      return `Must be at least ${min} characters`;
+    }
+    return null;
+  }
+
+  static MaxLength(value, max) {
+    if ((value.length > max)) {
+      return `Must be at most ${max} characters`;
+    }
+    return null;
+  }
+
+  static Email(value) {
+    return (() => {
+  const __subject0 = value;
+  if (new RegExp("^[^@\\s]+@[^@\\s]+\\.[^@\\s]+$").test(__subject0)) {
+    return null;
+  }
+  else {
+    return "Must be a valid email";
+  }
+})();
+  }
+
+  static Min(value, min) {
+    if ((value < min)) {
+      return `Must be at least ${min}`;
+    }
+    return null;
+  }
+
+  static Max(value, max) {
+    if ((value > max)) {
+      return `Must be at most ${max}`;
+    }
+    return null;
+  }
+}

package/src/forms.ks

@@ -0,0 +1,77 @@
+// FormField<T>: a single form input's value, validation state, and touched
+// flag, built on the same state<T> reactivity Component already uses — no
+// new reactive primitive, and deliberately no DOM binding of its own
+// (wiring Value to a real <input> is one addEventListener call in your own
+// Render(), the same as Counter's own click handler — see Kopular's README).
+//
+// A validator is a plain (T) => string? function: null means valid, the
+// same "null means nothing to report" convention KopScript's nullable
+// types already use elsewhere. There's no array of validators — KopScript
+// has no syntax for an array of function values — so combining more than
+// one check is just an if-chain in one lambda:
+//
+//   FormField<string> name = new FormField<string>("", (string v) => {
+//     string? required = Validators.Required(v);
+//     if (required != null) { return required; }
+//     return Validators.MaxLength(v, 40);
+//   });
+class FormField<T> {
+  public state<T> Value;
+  public state<string?> Error;
+  public state<bool> Touched;
+
+  constructor(T initial, (T) => string? validate) {
+    this.Value = state(initial);
+    this.Error = state(validate(initial));
+    this.Touched = state(false);
+    this.Value.Subscribe((T v) => { this.Error.Value = validate(v); });
+  }
+
+  // Call on blur — separate from Error so a fresh, untouched field with an
+  // invalid initial value (e.g. Required on an empty string) doesn't show
+  // an error message before the user has had a chance to type anything.
+  public void Touch() {
+    this.Touched.Value = true;
+  }
+
+  public bool Valid() {
+    return this.Error.Value == null;
+  }
+}
+
+// A small set of common checks, each returning an error message or null —
+// not a validation framework, just the handful of checks almost every form
+// needs, so most fields don't have to hand-write string-length arithmetic.
+class Validators {
+  public static string? Required(string value) {
+    if (value.Trim().Length == 0) { return "Required"; }
+    return null;
+  }
+
+  public static string? MinLength(string value, number min) {
+    if (value.Length < min) { return $"Must be at least {min} characters"; }
+    return null;
+  }
+
+  public static string? MaxLength(string value, number max) {
+    if (value.Length > max) { return $"Must be at most {max} characters"; }
+    return null;
+  }
+
+  public static string? Email(string value) {
+    return match value {
+      r"^[^@\s]+@[^@\s]+\.[^@\s]+$" => null,
+      _ => "Must be a valid email"
+    };
+  }
+
+  public static string? Min(number value, number min) {
+    if (value < min) { return $"Must be at least {min}"; }
+    return null;
+  }
+
+  public static string? Max(number value, number max) {
+    if (value > max) { return $"Must be at most {max}"; }
+    return null;
+  }
+}