From a710d891d4a168caef4522d9b87ad3f048d651dd Mon Sep 17 00:00:00 2001 From: GenericJam Date: Sat, 4 Jul 2026 20:29:10 -0600 Subject: [PATCH] docs: fix undefined tap/1 in getting_started "first screen" example MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit The example used `on_tap={tap(:increment)}`, but no `tap/1` exists — `use Mob.Screen` imports the sigil, not a `tap` helper — so pasting the getting- started example produced a compile error (GH #46). Use the canonical inline tuple `on_tap={{self(), :increment}}` (matches `Mob.Sigil`'s own docstring, screen_lifecycle.md, and device_capabilities.md), which the existing `handle_info({:tap, :increment}, ...)` already handles. Added a clause to the walkthrough explaining the `{self(), :increment}` → `{:tap, :increment}` wiring. Verified: the corrected module compiles and renders a valid tree. Closes #46. Co-Authored-By: Claude Opus 4.8 (1M context) --- guides/getting_started.md | 7 ++++--- 1 file changed, 4 insertions(+), 3 deletions(-) diff --git a/guides/getting_started.md b/guides/getting_started.md index b88e26c0..ea8da311 100644 --- a/guides/getting_started.md +++ b/guides/getting_started.md @@ -632,7 +632,7 @@ defmodule MyApp.HomeScreen do ~MOB""" -