Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

[Feature] 通知栏合并重复消息并显示次数

Closed Beginner friendly
  • Is something wrong?
#1,092 0 comments 0 reactions 0 assignees View on GitHub

Maintainers usually reply within 1 day

Nobody has claimed this yet.

Assessment

Difficulty
2/5
Estimated time
1-3 hours
Newbie friendliness
72/100
Issue type
Feature
Clarity
Clearly specified
Activity status
Active
Tech stack
typescript
Domain
frontend

Research direction

Locate the notification store/service that pushes entries into the notification bar (search for where notification items are added and rendered, likely under the renderer/UI code). Add deduplication by message text with an incrementing count, and render the （2） suffix in the notification list item. Done = the four acceptance criteria hold: identical messages collapse to one entry with a counter, differing messages stay separate; verify by triggering the same notification repeatedly.

Written by the indexing model from the issue text.

Description

area:ui enhancement issue-form:feature platform:cross-platform review: high
Problem to solve / 要解决的问题

通知栏中重复出现相同消息时，多条内容相同的通知容易刷屏，占用列表空间，也不方便查看其他消息。

Proposed solution / 建议方案

希望通知栏可以合并重复消息：相同通知只保留一条，并在消息后显示累计出现次数，例如 xxxx（2）。

  • 首次出现时正常显示 xxxx。
  • 相同通知第二次出现时，更新为 xxxx（2），不新增重复条目。
  • 后续重复出现时继续累计为 xxxx（3）、xxxx（4） 等。
  • 内容不同的通知保持独立，不误合并。
Target platform / 目标平台

Cross-platform / 跨平台

希望各平台的通知栏提供一致的合并与计数体验；未限定具体平台。

Area / 模块

UI / 界面

Priority / 优先级

未指定，交由维护者评估。

Alternatives considered / 已考虑的替代方案

暂无。

Additional context / 补充信息

显示示例：同一条 xxxx 通知出现两次后，列表中显示一条 xxxx（2）。

验收标准：

  • 首次通知正常显示。
  • 相同通知第二次出现后，仅保留一条并显示 （2）。
  • 后续重复通知继续累加次数，不产生重复条目。
  • 不同内容的通知不会被误合并。
Checklist / 提交前检查
  • I searched existing issues for duplicates. / 我已搜索现有 Issue，确认没有重复建议。
Dominant language
TypeScript
Stars
1.8k
Forks
151
Avg merge
7h 51m
Merged PRs (30d)
351

Getting set up

This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from 1lck/Lithe-IDEA

All issues in 1lck/Lithe-IDEA

Similar issues

More TypeScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.