如何统一 sdk 和 编辑器 自定义组件的注册方式?
- Dominant language
- TypeScript
- Stars
- 18.9k
- Forks
- 2.7k
- PR merge metrics
- No merged PRs in 30d
Description
#### 实现场景:
想通过一套代码分别实现 sdk 和 编辑器 里自定义组件的能力
#### 存在的问题:
目前官方文档里,描述 "基于 custom 组件可以直接在 amis 配置实现自定义功能,它的支持面最广,是唯一支持在可视化编辑器中使用的方法。",也就是说目前只有使用 custom 组件临时扩展,这种方式才能同时支持在 sdk 和 编辑器里使用。但是这种方式显然不满足真实的需求,业务里更需要的是,类似于自己统一封装一套组件库,然后同时在sdk和编辑器使用这种方式
#### 当前方案:
请粘贴你当前方案的完整 amis schema 代码...
Contributor guide
No contributing guide indexed for this repository
Research direction
Start by reviewing the official custom component documentation and comparing how components are registered in the SDK and the visual editor. Identify the existing registration entry points and the constraints of the custom component approach. Done would mean a documented, unified registration path that supports the same component library in both environments, with agreement on the required API.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript
- Domain
- frontend
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100