jd-opensource / jd-opensource/taro-ui
建议：组件list、card等很多组件为什么api几乎都不能传jsx？？？？
Open
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 4.7k
- Forks
- 740
- PR merge metrics
- No merged PRs in 30d
Description
### 这个功能解决了什么问题？
扩展性高
### 你期望的功能是怎样的？
api可以传jsx
### 补充信息
string局限性太大了，除非和你ui长的一样，有点区别就用不了了
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 concerns the APIs of components such as List and Card, but it names no files, tests, or entry points. Start by locating those component API definitions and reviewing how they currently handle string content. Done should mean the relevant component APIs can accept JSX where the current string-only limitation prevents customization, with coverage for the changed behavior.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- react, typescript
- Domain
- frontend
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100