-
Notifications
You must be signed in to change notification settings - Fork 100
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
update url #26
base: master
Are you sure you want to change the base?
update url #26
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
我们这里也遇到了这个问题, |
@sunteya 所以我的理解是这个PR(使用oauth2/authorize)的改动你已经测试过了,可以直接发布,对吗? |
场景一 场景二 上面的图片分别以场景一及场景二作为下文引用说明: 场景二为是目前 gem 的行为,是微信开放平台来源,使用的 URL 为 我个人比较偏向于通过 题外话,如果使用
|
开放平台的有专门的 gem 包: https://github.com/mycolorway/omniauth-open-wechat-oauth2 所以这边只用在场景一。 |
看来 README.md 要大改动了。 |
@NeverMin 如果支持两个场景, 那就明确区分开。两个 URL,还可以讲一下如何支持 unionid . |
新版本的微信公众号授权修改了 BASE URL,我的PR进行了更新。
同时,稍优化了一下 README