Skip to content

Conversation

yenharvey
Copy link
Contributor

Summary

Add qq connector.

Testing

I have manually tested the QQ connector by:

  • Setting up the QQ connector in the Logto management console with the necessary App ID and App Secret.
  • Initiating the sign-in flow with the QQ connector on a test application.
  • Successfully authenticating with a QQ account and being redirected back to the application with user information.
  • Tested the sign-up flow with a new QQ account.
  • Verified the user information retrieved from QQ (e.g., nickname, avatar).

Checklist

  • .changeset
  • unit tests
  • integration tests
  • necessary TSDoc comments

image
image
image

yenharvey added 3 commits May 12, 2025 21:16
Signed-off-by: Yen Harvey <2117555041@qq.com>
Signed-off-by: Yen Harvey <2117555041@qq.com>
Signed-off-by: Yen Harvey <2117555041@qq.com>
@yenharvey yenharvey requested review from darcyYe and gao-sun as code owners May 12, 2025 13:28
Copy link

github-actions bot commented May 12, 2025

COMPARE TO master

Total Size Diff ⚠️ 📈 +25.68 KB

Diff by File
Name Diff
.changeset/red-rules-cheat.md 📈 +70 Bytes
packages/connectors/connector-qq/README.md 📈 +2.25 KB
packages/connectors/connector-qq/README.zh-CN.md 📈 +1.9 KB
packages/connectors/connector-qq/logo.svg 📈 +2.46 KB
packages/connectors/connector-qq/package.json 📈 +1.64 KB
packages/connectors/connector-qq/src/constant.ts 📈 +2.35 KB
packages/connectors/connector-qq/src/index.test.ts 📈 +3.91 KB
packages/connectors/connector-qq/src/index.ts 📈 +8.19 KB
packages/connectors/connector-qq/src/mock.ts 📈 +998 Bytes
packages/connectors/connector-qq/src/types.ts 📈 +1.77 KB
pnpm-lock.yaml 📈 +178 Bytes

@cheezone
Copy link

cheezone commented May 13, 2025

Hi @gao-sun @darcyYe @wangsijie, just a gentle follow-up on this PR. The changes here would be really helpful for our current workflow, and we’d greatly appreciate your review when you have a moment. Thanks so much for your time and expertise!

@cheezone
Copy link

@yenharvey Noticed the QQ logo image is quite large and takes ~3s to load on 4G. Could we optimize it (e.g., compress/resize) for faster mobile loading? Thanks!

@yenharvey
Copy link
Contributor Author

@cheezone I've reduced the logo size to 2.5k.

@darcyYe
Copy link
Contributor

darcyYe commented May 13, 2025

Thanks for you contribution

@yenharvey
Copy link
Contributor Author

I've addressed all the feedback by adding detailed API comments to the endpoints and functions and removed the duplicate CHANGELOG.md file as it will be auto-generated by the changeset. Thank you!

@cheezone
Copy link

@yenharvey I noticed that you seem to have already submitted the changes, addressing the review comments. Is it necessary to re-request review?

Copy link
Member

@charIeszhao charIeszhao left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I reviewed the updated changes and it all looks good to me now. Thanks again for the contribution and quick response.

@darcyYe Leaving it to you for the final approval.

@charIeszhao
Copy link
Member

There seems to be a frozen lockfile issue in your branch. Please take a look at the CI error logs and execute the suggested CLI commands. @yenharvey

@yenharvey
Copy link
Contributor Author

@charIeszhao I've executed the suggested command from the CI logs: pnpm install --no-frozen-lockfile to update the lockfile. I noticed that 'logo-dark.svg' was automatically added back during this process. To avoid any further issues, I've decided to keep it rather than removing it again. The updated lockfile and package.json have been pushed to the branch.

@yenharvey
Copy link
Contributor Author

@cheezone Yes, this is my first time submitting a PR. I initially started development on the main branch, but later learned it's better practice to use a feature branch for PR development. So I created this new PR with all the changes properly implemented on a dedicated branch. All review comments have been addressed in this PR. I learn the proper workflow. The PR should be ready for review now. Thanks!

@cheezone
Copy link

@darcyYe Hello, could you please ask if there's a chance for this PR to be reviewed in the near future? This change is quite helpful for me as well, thank you for your hard work!

Copy link
Contributor

@darcyYe darcyYe left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

Copy link
Member

@gao-sun gao-sun left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

lgtm on changeset

@charIeszhao charIeszhao merged commit 2f8f9d6 into logto-io:master May 19, 2025
34 checks passed
@yenharvey
Copy link
Contributor Author

yenharvey commented May 21, 2025 via email

@yenharvey
Copy link
Contributor Author

yenharvey commented May 21, 2025 via email

@cheezone
Copy link

@yenharvey

It's okay, it's resolved. It was just about the UnionID. However, the QQ connector seems strange to me. It might be a problem with QQ. I did a test on the mobile device. It can't launch the QQ mobile app. Instead, it shows a desktop version page asking the user to scan a QR code. After the user scans the code and agrees, it fails to redirect successfully.

@yenharvey
Copy link
Contributor Author

@cheezone Scared me! I thought we were having that awkward "Works only on my machine" situation. This behavior on mobile is actually normal, as my implementation is targeted for web development. I remember mobile needs an extra parameter passed in. Since I wasn't sure if logto had an API to detect platforms, I just temporarily solved the issue of having a QQ connector😜.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Development

Successfully merging this pull request may close these issues.

5 participants