Change Proposal: Snackbar notification system
维护者通常 2 天内回复
还没有人认领这个 Issue。
评估
- 难度
- 5/5
- 预计耗时
- 一周以上
- 新手友好度
- 38/100
- Issue 类型
- 功能
- 描述清晰度
- 基本清楚
- 活跃度
- 活跃
- 技术栈
- react, typescript
调研方向
Start by reviewing the MuiSnackbar, MuiSnackbarContent, and MuiAlert overrides in DiamondDSTheme.ts, along with the Snackbar story. Compare the proposed SnackbarProvider approach with the existing component usage and define how stacking, queueing, theming, and notification guidance should fit together. Done means the accepted design is implemented with usage documentation covering placement, duration, severity, and inline Alert choices.
由索引模型根据 Issue 内容生成。
描述
What is being proposed?
Introduce a snackbar notification system for stacking and queueing multiple notifications (e.g. notistack or an equivalent MUI-compatible library), plus written guidance on when and how to use it.
(was raised by several issues in i15-1/Atlas project)
Why is this needed?
Today the DS only themes MUI's bare Snackbar/Alert (see MuiSnackbar/MuiSnackbarContent/MuiAlert overrides in DiamondDSTheme.ts and the Snackbar story). Each consumer wires its own open state and there's no way to stack or queue multiple notifications, and no guidance on when a snackbar is appropriate versus an inline Alert.
MUI/Material's own guidance recommends showing only one snackbar at a time, but our platform needs to support multiple concurrent, stacked notifications, as seen in systems such as IBM Carbon's notification component.
What will change?
- Behaviour: adds a
SnackbarProvider(or similar) enabling stacking/queueing of multiple notifications - Component props or usage: consumers trigger notifications imperatively instead of managing
openstate themselves - New dependency: notistack (or equivalent), themed to match existing
MuiAlert/MuiSnackbarContentstyling - Documentation: usage guidance covering when to use a snackbar vs. inline
Alert, severity/variant mapping, duration and placement conventions
Interface changes (if any)
const { enqueueSnackbar } = useSnackbar();
enqueueSnackbar("Saved", { variant: "success" });
Breaking change?
- No
Next steps
A maintainer will review this issue.
If accepted, it will be marked as accepted and a PR may then be opened.
- 主要语言
- TypeScript
- 星标
- 9
- 派生
- 3
- 平均合并
- 6 天 7 小时
- 30 天内合并 PR
- 20
环境准备
在浏览器里用你自己的 GitHub 账号启动这个项目的开发容器。
- 没有 Dockerfile 或 Docker Compose 文件
- 没有 Pull Request 模板
- 阅读贡献指南
从这里开始
- 先读完整个 Issue，再读项目的贡献指南。
- 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
- Fork 仓库，在一个分支上完成修改。
- 提交 Pull Request，并在描述里引用这个 Issue 编号。
DiamondLightSource/sci-react-ui 的其他 Issue
-
needs-triage
难度 2/5 1-3 小时 新手友好度 75/100
DiamondLightSource/sci-react-ui#325 · 1 条评论 ·
维护者通常 2 天内回复
-
accepted
难度 2/5 1-3 小时 新手友好度 72/100
DiamondLightSource/sci-react-ui#283 ·
维护者通常 2 天内回复
-
needs-triage
难度 5/5 一周以上 新手友好度 35/100
DiamondLightSource/sci-react-ui#331 ·
维护者通常 2 天内回复
-
needs-triage
难度 4/5 3-5 天 新手友好度 55/100
DiamondLightSource/sci-react-ui#324 ·
维护者通常 2 天内回复
-
needs-triage
难度 5/5 一周以上 新手友好度 45/100
DiamondLightSource/sci-react-ui#280 ·
维护者通常 2 天内回复
查看 DiamondLightSource/sci-react-ui 的全部 Issue
相似的 Issue
-
bug via-triage
难度 2/5 1-3 小时 新手友好度 78/100
pingdotgg/t3code#14452 · 1 条评论 ·
维护者通常 1 天内回复
-
难度 2/5 1-3 小时 新手友好度 75/100
solana-foundation/program-examples#747 · 1 条评论 ·
维护者通常 9 天内回复
-
难度 2/5 1-3 小时 新手友好度 65/100
remotion-dev/remotion#11847 ·
维护者通常 1 天内回复
-
bug
难度 2/5 1-3 小时 新手友好度 78/100
openwatersio/slackwater#355 ·
维护者通常 1 天内回复
-
bug
难度 2/5 1-3 小时 新手友好度 74/100
melgarafael/DeskcommCRM#1998 · 3 条评论 ·
维护者通常 1 天内回复