Skip to content

fix: correct Composer import path in docs#18

Merged
kravetsone merged 3 commits into
gramiojs:mainfrom
ttempaa:fix/composer-import-typo
Mar 12, 2026
Merged

fix: correct Composer import path in docs#18
kravetsone merged 3 commits into
gramiojs:mainfrom
ttempaa:fix/composer-import-typo

Conversation

@ttempaa
Copy link
Copy Markdown
Contributor

@ttempaa ttempaa commented Mar 12, 2026

Replace import { Composer } from "@gramio/composer" with import { Composer } from "gramio" across user-facing docs. The @gramio/composer package is an internal utility — users should import Composer from gramio.

@kravetsone kravetsone merged commit 95d321a into gramiojs:main Mar 12, 2026
1 check passed
@ttempaa ttempaa deleted the fix/composer-import-typo branch March 12, 2026 21:50
kravetsone added a commit that referenced this pull request Apr 22, 2026
Adds a reference-level playbook for what to render and why, not just how
to call the API: hero /start, edit-in-place navigation, nested menus with
breadcrumbs + Back/Home, toggle buttons (label-is-state), destructive
confirm flows, ctx.answer() discipline, loading/empty states, command
discovery via setMyCommands, reply vs inline tradeoffs, formatting
hierarchy, deep links, and a ship checklist.

Includes a runnable ux-menu example + test demonstrating the patterns
(hero, nested menu, toggles, destructive confirm), plus Critical
Concept #18 in SKILL.md and cross-refs from keyboards.md / views.md.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants