tutuca 0.9.94 → 0.9.95

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "tutuca",
-  "version": "0.9.94",
+  "version": "0.9.95",
   "type": "module",
   "description": "Zero-dependency SPA framework with immutable state and virtual DOM",
   "main": "./dist/tutuca.js",

package/skill/tutuca/core.md

@@ -586,6 +586,15 @@ The content of `value` depends on the event source:
 For numeric inputs, prefer `valueAsInt` / `valueAsFloat` to skip the
 string parse.
 
+Ask for the most granular arg the handler actually uses — `value` /
+`valueAsInt` / `key`, not the raw `event` — when the specific value is
+all you need. A handler that takes `event` forces every test and
+storybook story to fabricate a DOM-event-shaped object
+(`{ target: { value: … } }`); one that takes `value` is called with a
+plain literal. (Genuine exceptions exist — e.g. a file input needs
+`event` to reach `event.target.files`.) See
+[testing.md](./testing.md) *Designing handlers so tests stay simple*.
+
 ### Event Modifiers
 
 `@on.<event>+<mod>+<mod>=...`

package/skill/tutuca/patterns/coordinate-components.md

@@ -24,3 +24,8 @@ selections); **send/receive** to address one known component
 `scope.registerRequestHandlers({...})`, and `response` gets `(res, err)`. `ctx`
 is always the trailing arg. `receive.init` is a convention, not a lifecycle
 hook — dispatch it with `app.sendAtRoot("init")`.
+
+Carry the most granular payload across the channel, not whole objects you
+won't use — `ctx.bubble("itemSelected", [item.label])` over passing the entire
+component. The handler then receives plain values that are easy to reproduce in
+tests and storybook stories.

package/skill/tutuca/patterns/handle-events.md

@@ -25,3 +25,10 @@ names — `value`, `valueAsInt`/`valueAsFloat`, `event`, `key`, `isAlt`,
 `event.target.value` (or `.checked` for a checkbox, or `event.detail` for a
 `CustomEvent`). Bind events declaratively with `@on.` rather than reaching for
 the node and `addEventListener` — an outside listener bypasses the transactor.
+
+Pass the most granular arg the handler needs — `value`/`valueAsInt`/`key`, not
+the raw `event` — when the specific value is all the handler uses. The args
+become plain literals, so the same call is trivial to reproduce in tests and
+storybook stories (no need to stub a `{ target: { value: … } }` event). Reach
+for `event` only when you truly need it (e.g. a file input reading
+`event.target.files`).