- 
                Notifications
    
You must be signed in to change notification settings  - Fork 559
 
feat: wechat provider #1630
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
base: master
Are you sure you want to change the base?
feat: wechat provider #1630
Conversation
* feat: add huawei cloud msgsms support * fix: huawei cloud msgsms * fix: return msgId instead of response body when operation is successful * fix: ci * fix * chore * chore: setup struct tag split_words for huawei_cloud configuration Signed-off-by: Zhou Zhiqiang <[email protected]> --------- Signed-off-by: Zhou Zhiqiang <[email protected]> Co-authored-by: Zhou Zhiqiang <[email protected]>
| 
           Looks nice at a first glance. Given that WeChat is a huge user base, we're considering adding this. I'll do a proper review soon.  | 
    
| 
           Any updates?  | 
    
          
 Nothing  | 
    
| 
           Any updates? It looks like AliYun (Alibaba) from China forked Supabase and added WeChat and Alipay, created what's called "AnalyticDB for PostgreSQL" service on their Cloud provider platform. https://help.aliyun.com/zh/analyticdb/analyticdb-for-postgresql/user-guide/using-supabase-to-implement-third-party-login. This was just around Aug/Sep of 2025.  | 
    
What kind of change does this PR introduce?
Bug fix, feature, docs update, ...
What is the current behavior?
Please link any relevant issues here.
What is the new behavior?
Feel free to include screenshots if it includes visual changes.
Additional context
Add any other context or screenshots.