You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Recently while working on wechaty-puppet-padpro project, I found that there is a way to get the real wechat id from underlying service. So for each contact, there will be two ids, one is wxid, which is allocated by wechat system, the other one is the use name, which is created by the user.
I am suggesting here to have an optional customId field on Contact class. For developers who want to get the real wechat id, they could try to get the customId first, then fallback to the id, in this way, they will get the id that same as the one on wechat.
Does this make sense?
The text was updated successfully, but these errors were encountered:
Recently while working on
wechaty-puppet-padpro
project, I found that there is a way to get the real wechat id from underlying service. So for each contact, there will be two ids, one is wxid, which is allocated by wechat system, the other one is the use name, which is created by the user.I am suggesting here to have an optional
customId
field onContact
class. For developers who want to get the real wechat id, they could try to get thecustomId
first, then fallback to theid
, in this way, they will get the id that same as the one on wechat.Does this make sense?
The text was updated successfully, but these errors were encountered: