mirror of
https://github.com/hiaaryan/sileo.git
synced 2026-04-26 15:35:54 +03:00
[GH-ISSUE #5] [Discussion] Toast button philosophy: When should toasts be actionable / shareable #4
Labels
No labels
bug
enhancement
pull-request
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/sileo#4
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @YogeshK34 on GitHub (Feb 15, 2026).
Original GitHub issue: https://github.com/hiaaryan/sileo/issues/5
Context
I've been thinking about the button functionality in toasts and wanted to open a discussion about UX philosophy.
The Question
Toasts are traditionally ephemeral notifications, but Sileo supports buttons with
onClickhandlers. This opens up possibilities like "Share" buttons, but it also raises questions:Examples
✅ Good: "Screenshot captured" → Share button (shares the artifact)
❌ Questionable: "Settings saved" → Share button (nothing meaningful to share)
Thoughts?
Would love to hear the maintainer's perspective and community thoughts on this! Is there a philosophy behind the button API, or is it intentionally unopinionated?
typetosileo.show()for dynamic toast state #30