@colixsystems/widget-sdk 0.149.0 → 0.150.0

package/README.md

@@ -72,7 +72,32 @@ See the design reference for the full architecture: [`docs/architecture/widget-m
 
 ## Status
 
-`v0.148.0` — pre-publish. The package surface (types, function names, export paths) is the v1 contract; runtime behaviour for some hooks is stubbed (each hook documents what's wired and what isn't). It is **not yet published to npm**.
+`v0.149.0` — pre-publish. The package surface (types, function names, export paths) is the v1 contract; runtime behaviour for some hooks is stubbed (each hook documents what's wired and what isn't). It is **not yet published to npm**.
+
+### What's new in 0.149.0 (contract 1.117.0)
+
+**New primitive `<EmojiPicker>` — pick an emoji without leaving for the OS keyboard (sc-8104).** Typed emoji always worked: a plain `<TextInput>` stores and renders them on both hosts, and nothing about that changes. What was missing was an in-app way to *choose* one — for a message composer, or to react to something.
+
+```jsx
+const [open, setOpen] = useState(false);
+const [recents, setRecents] = useState([]);
+
+<EmojiPicker
+  visible={open}
+  recents={recents}
+  onRecentsChange={setRecents}
+  onRequestClose={() => setOpen(false)}
+  onSelect={(char) => {
+    const { value } = insertAtCaret(draft, char, selection);
+    setDraft(value);
+    setOpen(false);
+  }}
+/>
+```
+
+It presents inside `<Overlay>`, so it escapes the widget's clipping box on both hosts, and ships a curated Unicode set (categories, search, recents) as plain data — no emoji dependency to vet. `onSelect` hands you the character; `recents` / `onRecentsChange` let you persist the picks wherever your widget keeps state. Pair it with `insertAtCaret(value, char, selection)` to land the emoji mid-draft instead of appending it.
+
+**Also new: a shared reaction model.** `groupReactions(rows, { typeField, userField, userId })` turns reaction rows into per-emoji pill groups — one row per (target, user, emoji), de-duplicated per user — and `readReactionEmoji(value)` maps a stored value to its emoji, ignoring anything it does not recognise. Widgets storing reactions should group through these rather than rolling their own, so pills behave identically wherever they appear.
 
 ### What's new in 0.148.0 (contract 1.116.0)
 

package/dist/contract.cjs

@@ -2079,6 +2079,15 @@ const PRIMITIVES = [
     rnComponent: null,
     docsUrl: null,
   },
+  // sc-8104 — the in-app emoji picker. Typed emoji always worked; what this
+  // replaces is being forced out to the OS keyboard to find one.
+  {
+    name: "EmojiPicker",
+    description:
+      "In-app emoji picker. `<EmojiPicker visible={open} onRequestClose={() => setOpen(false)} onSelect={(char) => insert(char)} recents={recents} onRecentsChange={setRecents} />`. THE way to let an app user pick an emoji without leaving for the OS keyboard — for a message/post composer, and for starting a reaction. It presents inside the SDK `<Overlay>`, so it escapes the clipping box of the widget on both hosts, and it ships a curated Unicode set WITH the SDK (categories, search, recents) so no emoji dependency is needed. Props: `visible` (boolean), `onSelect` (`(char: string) => void`, fired with the chosen emoji character), `onRequestClose` (wire it or the picker cannot be dismissed), `recents` (string[] of previously picked characters) and `onRecentsChange` (persist them where the widget keeps its own state), plus `accessibilityLabel` and `searchPlaceholder`. To insert into a composer at the caret rather than appending, pair it with `insertAtCaret(value, char, selection)`. Typed emoji need nothing: a plain `TextInput` already stores and renders them.",
+    rnComponent: null,
+    docsUrl: null,
+  },
   // sc-6970 — formatted content, rendered. Widgets have no HTML path on either
   // host, so this is the ONE way bold, headings and lists reach a reader.
   {
@@ -4243,7 +4252,15 @@ const CONTRACT = deepFreeze({
   //    hosts' shared textStyle module), not a theme token. Additive: no export
   //    changed signature, and a theme carrying no `roles` renders on the seeded
   //    defaults exactly as before.
-  version: "1.117.0",
+  // 1.118.0: additive (sc-8104) — the `EmojiPicker` primitive, plus the emoji
+  //    set and reaction model it ships with. Typed emoji always worked; there
+  //    was no in-app way to PICK one, so every emoji meant a trip to the OS
+  //    keyboard. The curated Unicode set ships as plain string data rather than
+  //    a vetted dependency. `groupReactions` / `readReactionEmoji` are shared
+  //    because Newsfeed and Chat both render per-emoji pills over a Reactions
+  //    table, and the legacy slug mapping (`like` -> emoji) must not be
+  //    re-derived per widget.
+  version: "1.118.0",
   sharedTranslationKeys: SHARED_TRANSLATION_KEYS,
   hooks: HOOKS,
   primitives: PRIMITIVES,

package/dist/contract.js

@@ -2079,6 +2079,15 @@ const PRIMITIVES = [
     rnComponent: null,
     docsUrl: null,
   },
+  // sc-8104 — the in-app emoji picker. Typed emoji always worked; what this
+  // replaces is being forced out to the OS keyboard to find one.
+  {
+    name: "EmojiPicker",
+    description:
+      "In-app emoji picker. `<EmojiPicker visible={open} onRequestClose={() => setOpen(false)} onSelect={(char) => insert(char)} recents={recents} onRecentsChange={setRecents} />`. THE way to let an app user pick an emoji without leaving for the OS keyboard — for a message/post composer, and for starting a reaction. It presents inside the SDK `<Overlay>`, so it escapes the clipping box of the widget on both hosts, and it ships a curated Unicode set WITH the SDK (categories, search, recents) so no emoji dependency is needed. Props: `visible` (boolean), `onSelect` (`(char: string) => void`, fired with the chosen emoji character), `onRequestClose` (wire it or the picker cannot be dismissed), `recents` (string[] of previously picked characters) and `onRecentsChange` (persist them where the widget keeps its own state), plus `accessibilityLabel` and `searchPlaceholder`. To insert into a composer at the caret rather than appending, pair it with `insertAtCaret(value, char, selection)`. Typed emoji need nothing: a plain `TextInput` already stores and renders them.",
+    rnComponent: null,
+    docsUrl: null,
+  },
   // sc-6970 — formatted content, rendered. Widgets have no HTML path on either
   // host, so this is the ONE way bold, headings and lists reach a reader.
   {
@@ -4239,7 +4248,15 @@ const CONTRACT = deepFreeze({
   //    hosts' shared textStyle module), not a theme token. Additive: no export
   //    changed signature, and a theme carrying no `roles` renders on the seeded
   //    defaults exactly as before.
-  version: "1.117.0",
+  // 1.118.0: additive (sc-8104) — the `EmojiPicker` primitive, plus the emoji
+  //    set and reaction model it ships with. Typed emoji always worked; there
+  //    was no in-app way to PICK one, so every emoji meant a trip to the OS
+  //    keyboard. The curated Unicode set ships as plain string data rather than
+  //    a vetted dependency. `groupReactions` / `readReactionEmoji` are shared
+  //    because Newsfeed and Chat both render per-emoji pills over a Reactions
+  //    table, and the legacy slug mapping (`like` -> emoji) must not be
+  //    re-derived per widget.
+  version: "1.118.0",
   sharedTranslationKeys: SHARED_TRANSLATION_KEYS,
   hooks: HOOKS,
   primitives: PRIMITIVES,