Tencent / Tencent/tdesign-mobile-react
[FR] 希望将Dom操作都封装在一个文件，并使用异步方式，方便适配平台
Open
Nobody has claimed this yet.
💪🏻 enhancement
hard
issueshoot
🧐 unconfirmed
- Dominant language
- TypeScript
- Stars
- 105
- Forks
- 97
- Avg merge
- 4h 26m
- Merged PRs (30d)
- 22
Description
这个功能解决了什么问题
我在尝试将Tdesign-mobile-react用在Taro平台，目前大部分组件都已经跑通，移植过程中发现Tdesign-mobile-react的dom操作比较零碎，util文件夹下有dom接口的封装，但是大部分组件都没有使用。 导致移植需要修改的文件蛮多，但是大部分都是Dom操作，如果能把Dom操作给统一封装起来就太好了。
Taro没有好用的组件库，Tdesign维护积极，底层架构也很棒，很希望Tdesign能在Taro平台运行
你建议的方案是什么
dom操作统一封装，并采用异步方式
IssueShoot
- 预估时长: 5
- 期望完成时间: 2026-01-30 00:00:00 +0000 UTC
- 开发难度: 高
- 参与人数: 1
- 需求对接人: anlyyao
- 验收标准: 实现期望改造效果，提 PR 并通过验收无误
- 备注: 最终激励以实际提交
pull request并合并为准
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
The issue points to the util folder's DOM wrappers and scattered DOM operations in the components; start by auditing those existing wrappers and their call sites. Determine the cross-component scope and asynchronous behavior needed for Taro compatibility. Done means the affected DOM operations are unified as requested and the resulting PR passes maintainer acceptance.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- react, typescript
- Domain
- frontend, mobile
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 28/100