-
Notifications
You must be signed in to change notification settings - Fork 2.5k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
contributeCommandCallParser() 对CommandCallParser的扩展不运作 #1860
Comments
经检查, 问题原因是内嵌的 |
Him188
added a commit
that referenced
this issue
Feb 17, 2022
… `priority`. Remove `builtinImplementations` and contribute them at the first initialization phase instead. Close #1888, fix #1860. Add `ComponentStorageInternal` for frontend to provide components. Deprecate: - SingletonExtension - SingletonExtensionPoint - AbstractSingletonExtensionPoint - SingletonExtensionSelector - CommandCallInterceptorProviderImpl - CommandCallInterceptorProviderImplLazy - CommandCallParserProviderImpl - CommandCallParserProviderImplLazy - CommandCallResolverProviderImpl - CommandCallResolverProviderImplLazy ABI breaking change: `PermissionServiceProvider.ExtensionPoint`: supertype changed from `AbstractSingletonExtensionPoint` to `AbstractInstanceExtensionPoint`.
Him188
added a commit
that referenced
this issue
Feb 17, 2022
… `priority`. Remove `builtinImplementations` and contribute them at the first initialization phase instead. Close #1888, fix #1860. Add `ComponentStorageInternal` for frontend to provide components. Deprecate: - SingletonExtension - SingletonExtensionPoint - AbstractSingletonExtensionPoint - SingletonExtensionSelector - CommandCallInterceptorProviderImpl - CommandCallInterceptorProviderImplLazy - CommandCallParserProviderImpl - CommandCallParserProviderImplLazy - CommandCallResolverProviderImpl - CommandCallResolverProviderImplLazy ABI breaking change: `PermissionServiceProvider.ExtensionPoint`: supertype changed from `AbstractSingletonExtensionPoint` to `AbstractInstanceExtensionPoint`.
Him188
added a commit
that referenced
this issue
Feb 17, 2022
… `priority`. Remove `builtinImplementations` and contribute them at the first initialization phase instead. Close #1888, fix #1860. Add `ComponentStorageInternal` for frontend to provide components. Deprecate: - SingletonExtension - SingletonExtensionPoint - AbstractSingletonExtensionPoint - SingletonExtensionSelector - CommandCallInterceptorProviderImpl - CommandCallInterceptorProviderImplLazy - CommandCallParserProviderImpl - CommandCallParserProviderImplLazy - CommandCallResolverProviderImpl - CommandCallResolverProviderImplLazy ABI breaking change: - `PermissionServiceProvider`: supertype changed - `CommandCallResolverProvider.ExtensionPoint`: supertype changed - `PermissionServiceProvider.ExtensionPoint`: supertype changed
Him188
added a commit
that referenced
this issue
Feb 22, 2022
… `priority`. Remove `builtinImplementations` and contribute them at the first initialization phase instead. Close #1888, fix #1860. Add `ComponentStorageInternal` for frontend to provide components. Deprecate: - SingletonExtension - SingletonExtensionPoint - AbstractSingletonExtensionPoint - SingletonExtensionSelector - CommandCallInterceptorProviderImpl - CommandCallInterceptorProviderImplLazy - CommandCallParserProviderImpl - CommandCallParserProviderImplLazy - CommandCallResolverProviderImpl - CommandCallResolverProviderImplLazy ABI breaking change: - `PermissionServiceProvider`: supertype changed - `CommandCallResolverProvider.ExtensionPoint`: supertype changed - `PermissionServiceProvider.ExtensionPoint`: supertype changed
Him188
added a commit
that referenced
this issue
Feb 24, 2022
… `priority`. Remove `builtinImplementations` and contribute them at the first initialization phase instead. Close #1888, fix #1860. Add `ComponentStorageInternal` for frontend to provide components. Deprecate: - SingletonExtension - SingletonExtensionPoint - AbstractSingletonExtensionPoint - SingletonExtensionSelector - CommandCallInterceptorProviderImpl - CommandCallInterceptorProviderImplLazy - CommandCallParserProviderImpl - CommandCallParserProviderImplLazy - CommandCallResolverProviderImpl - CommandCallResolverProviderImplLazy ABI breaking change: - `PermissionServiceProvider`: supertype changed - `CommandCallResolverProvider.ExtensionPoint`: supertype changed - `PermissionServiceProvider.ExtensionPoint`: supertype changed
已修复,现在可以使用预览版本 不知道为什么 GitHub 这个编辑框不能粘贴,预览版本用法可以在 开发文档-配置依赖-选择版本-预览版本 找到。 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
问题描述
即使使用
contributeCommandCallParser()
用自己的CommandCallParser
扩展,实际编译后插件依然使用SpaceSeparatedCommandCallParser
解析语句。即扩展方法完全没起到作用。(此外实测
contributeCommandCallResolver()
可以如期运作,因此合理猜测只有CommandCallParser
相关部分出了问题。)复现
不想透露现在的project,因此使用没有实际作用但更能反应问题的例子。
预期结果:
MyCommandCallParser.parse()
甚至未使用message
参数,因此无论输入如何都会被解析为stop指令。实际结果:语句正常解析。
mirai-core 版本
生产环境2.9.2,运行环境2.10.0-RC2
bot-protocol
ANDROID_PHONE
其他组件版本
无。
系统日志
网络日志
补充信息
No response
The text was updated successfully, but these errors were encountered: