nonebot / nonebot/plugin-alconna
[Feature] 关于GEWE适配器支持。
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 143
- Forks
- 27
- PR merge metrics
- No merged PRs in 30d
Description
请确认:
- [ x] 新特性的目的明确
- [ x] 我已经阅读了相关文档 并且找不到类似特性
Feature
概要
我最近正在将KOISHI的项目迁移到NONEBOT,我注意到在NONEBOT中对多适配器消息处理似乎很麻烦,alconna解决了很多这方面的问题。
我的项目中有使用到GEWE的服务,官方曾经也推出过该适配器 nonebot-adapter-gewe ,仓库已标注为不可用,我clone项目后对接口进行了更新以及适配当前的gewe系统已经可以正常使用该适配器。
我是否可以通过修改0.58.4(GEWE未被移除)的版本,通过修改适配器导入包已实现效果?
我修改了所有uniseg.adapters.gewechat下所有的原适配器包为我当前项目下的可用包后并没有反应。
08-22 05:41:22 [INFO] nonebot | Event will be handled by AlconnaMatcher(type='', module=src.plugins.test, lineno=17)
08-22 05:41:22 [INFO] nonebot | AlconnaMatcher(type='', module=src.plugins.test, lineno=17) running complete
是否已有相关实现
当前项目中已存在
其他内容
暂无
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
Start by inspecting the GEWE adapter integration in version 0.58.4, especially the uniseg.adapters.gewechat imports, and compare it with the updated nonebot-adapter-gewe mentioned in the issue. Reproduce the logged AlconnaMatcher run and determine the adapter changes needed for GEWE messages to be handled; done means the supported adapter works with the current GEWE system.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- api, backend
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 30/100