Category renaming bug
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 39k
- Forks
- 2.1k
- Avg merge
- 1d 4h
- Merged PRs (30d)
- 10
Description
Platform
Desktop - Windows
Describe the bug
https://github.com/user-attachments/assets/c38d2141-37b1-41b4-a038-30aac7739369
从演示视频一中可以清楚看到,将自动分组的 “x.com” 分类重命名为 “F” 后,视图中的所有来自【 X 】的订阅源都会自动归入 “F” 分类,即便之前曾进行过手动整理。
https://github.com/user-attachments/assets/0279577d-aa33-4ac4-bf30-071926695010
演示视频二中,将自动分组的 “weibo.com” 分类重命名为 “W” 后,视图内所有来自【微博】的订阅源均自动归入 “W” 分类,同时原先的分类已被自动删除。
Entry ID
No response
Relevant Information
No response
Reproduction Video
No response
Environment
App Version: 0.7.0
OS: Windows
User Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/138.0.0.0 Safari/537.36
Env: web
Browser: Chrome
Session Trace Id: hcPl0rgwhvCX4TFmBN7uc
Mode: production
Renderer: 0.7.0
Validations
- Check that there isn't already an issue that reports the same bug to avoid creating a duplicate.
- Check that this is a concrete bug. For Q&A, please open a GitHub Discussion instead.
- This issue is valid
Contributions
- I am willing to submit a PR to fix this issue
- I am willing to submit a PR with failing tests (actually just go ahead and do it, thanks!)
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reproducing the rename flow in Folo 0.7.0 on Windows using the two demonstrated cases: rename the automatically grouped “x.com” or “weibo.com” category after manually organizing feeds. Done means manually assigned feeds keep their existing categories, while only the intended automatic grouping changes; the issue provides no source file or test entry point to begin from.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript
- Domain
- desktop, frontend
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100