We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
无法使用这几个方法,看源码里面也去掉了,这种情况是怎么做条件筛选的。 .msgType("MSG_TYPE").event("EVENT").eventKey("EVENT_KEY").content("CONTENT")
类 WxCpTpMessageRouter
java.lang.Object me.chanjar.weixin.cp.tp.message.WxCpTpMessageRouter
public class WxCpTpMessageRouter extends Object 微信消息路由器,通过代码化的配置,把来自微信的消息交给handler处理 和WxCpMessageRouter的rule相比,多了infoType和changeType维度的匹配
说明:
使用方法: WxCpTpMessageRouter router = new WxCpTpMessageRouter(); router .rule() .msgType("MSG_TYPE").event("EVENT").eventKey("EVENT_KEY").content("CONTENT") .interceptor(interceptor, ...).handler(handler, ...) .end() .rule() .infoType("INFO_TYPE").changeType("CHANGE_TYPE") // 另外一个匹配规则 .end() ;
// 将WxXmlMessage交给消息路由器 router.route(message);
The text was updated successfully, but these errors were encountered:
配置路由规则时要按照从细到粗的原则,否则可能消息可能会被提前处理 这句话很重要
Sorry, something went wrong.
🎨 #1909 【企业微信】第三方应用路由规则类增加msgType和event的支持
55e1399
No branches or pull requests
简要描述
无法使用这几个方法,看源码里面也去掉了,这种情况是怎么做条件筛选的。
.msgType("MSG_TYPE").event("EVENT").eventKey("EVENT_KEY").content("CONTENT")
模块版本情况
详细描述
类 WxCpTpMessageRouter
java.lang.Object
me.chanjar.weixin.cp.tp.message.WxCpTpMessageRouter
public class WxCpTpMessageRouter
extends Object
微信消息路由器,通过代码化的配置,把来自微信的消息交给handler处理
和WxCpMessageRouter的rule相比,多了infoType和changeType维度的匹配
说明:
使用方法:
WxCpTpMessageRouter router = new WxCpTpMessageRouter();
router
.rule()
.msgType("MSG_TYPE").event("EVENT").eventKey("EVENT_KEY").content("CONTENT")
.interceptor(interceptor, ...).handler(handler, ...)
.end()
.rule()
.infoType("INFO_TYPE").changeType("CHANGE_TYPE")
// 另外一个匹配规则
.end()
;
// 将WxXmlMessage交给消息路由器
router.route(message);
The text was updated successfully, but these errors were encountered: