Skip to content

docs: fix undefined tap/1 in getting_started example (closes #46) #63

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
GenericJam merged 1 commit into from
Jul 5, 2026
Merged

docs: fix undefined tap/1 in getting_started example (closes #46) #63

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
7 changes: 4 additions & 3 deletions guides/getting_started.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -632,7 +632,7 @@ defmodule MyApp.HomeScreen do
~MOB"""
<Column padding={24} gap={16}>
<Text text={"Count: #{assigns.count}"} text_size={:xl} />
<Button text="Tap me" on_tap={tap(:increment)} />
<Button text="Tap me" on_tap={{self(), :increment}} />
</Column>
"""
end
Expand All @@ -646,8 +646,9 @@ end
```

`mount/3` initialises assigns. `render/1` returns the component tree via the `~MOB`
sigil. `handle_info/2` updates state in response to user events. After each update,
the framework calls `render/1` again and pushes the diff to the native layer.
sigil. An `on_tap={{self(), :increment}}` sends `{:tap, :increment}` to the screen
when the button is pressed, which `handle_info/2` matches to update state. After each
update, the framework calls `render/1` again and pushes the diff to the native layer.

---

Expand Down
Loading