[建议] 能否支持内容上的上下级？
Open
Nobody has claimed this yet.
- Dominant language
- C++
- Stars
- 13k
- Forks
- 1.3k
- Avg merge
- 14h 3m
- Merged PRs (30d)
- 3
Description
比如说有如下的层级
基础组件
| --- MySQL
| --- InnoDB
基础组件、MySQL、InnoDB 有各自的内容，而不仅仅是一个文件夹？
和 confluence 的展示结构是一样的
理由是：
- 如果时用于知识整理，这样可能会更符合知识的层级结构
- 目录树的结构同时也是知识的结构，不会有目录和文档分别展示的问题。
希望可以考虑下这个功能。不清楚会不会对底层的改动比较大。
Contributor guide
No contributing guide indexed for this repository
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
No files, tests, or entry points are named in the issue. Start by reviewing how VNote currently represents folders and note content, then define the scope for allowing hierarchy nodes to hold both their own content and child nodes. Done should support the Basic Components, MySQL, and InnoDB structure shown while preserving existing navigation.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- cpp
- Domain
- desktop
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 25/100