Reviewer's Guide

Adds missing QQ nickname retrieval support to the Vercel serverless API by wiring a new GET_QQ_NICK action to a dedicated handler that calls getQQNick with QQ_API_KEY and returns a standardized response.

Sequence diagram for GET_QQ_NICK QQ nickname retrieval via Vercel API

sequenceDiagram
  actor User
  participant Frontend
  participant VercelApi as Vercel_api_handler
  participant QQNickHandler as qqNickGet
  participant QQService as getQQNick
  participant QQApi as QQ_nickname_API

  User ->> Frontend: Trigger_get_QQ_nickname
  Frontend ->> VercelApi: POST { action: GET_QQ_NICK, qq }
  VercelApi ->> QQNickHandler: qqNickGet(event)
  QQNickHandler ->> QQService: getQQNick(qq, QQ_API_KEY)
  QQService ->> QQApi: HTTP_request_with_qq_and_key
  QQApi -->> QQService: nickname_response
  QQService -->> QQNickHandler: nick
  QQNickHandler -->> VercelApi: { code: SUCCESS, nick }
  VercelApi -->> Frontend: JSON_response
  Frontend -->> User: Display_nickname_or_error

Class diagram for Vercel API handler and QQ nickname retrieval function

classDiagram
  class VercelApiHandler {
    +handleRequest(request, response) Promise
    -config
    -RES_CODE
  }

  class QQNickHandler {
    +qqNickGet(event) Promise
    -validate(event, requiredFields)
  }

  class QQService {
    +getQQNick(qq, qqApiKey) Promise
  }

  class Config {
    +QQ_API_KEY
  }

  VercelApiHandler o-- QQNickHandler : calls_qqNickGet_on_GET_QQ_NICK
  QQNickHandler ..> QQService : calls_getQQNick
  QQNickHandler ..> Config : reads_QQ_API_KEY
  VercelApiHandler ..> Config : uses_config_for_other_actions

File-Level Changes

Interacting with Sourcery

• Trigger a new review: Comment @sourcery-ai review on the pull request.
• Continue discussions: Reply directly to Sourcery's review comments.
• Generate a GitHub issue from a review comment: Ask Sourcery to create an
  issue from a review comment by replying to it. You can also reply to a
  review comment with @sourcery-ai issue to create an issue from it.
• Generate a pull request title: Write @sourcery-ai anywhere in the pull
  request title to generate a title at any time. You can also comment
  @sourcery-ai title on the pull request to (re-)generate the title at any time.
• Generate a pull request summary: Write @sourcery-ai summary anywhere in
  the pull request body to generate a PR summary at any time exactly where you
  want it. You can also comment @sourcery-ai summary on the pull request to
  (re-)generate the summary at any time.
• Generate reviewer's guide: Comment @sourcery-ai guide on the pull
  request to (re-)generate the reviewer's guide at any time.
• Resolve all Sourcery comments: Comment @sourcery-ai resolve on the
  pull request to resolve all Sourcery comments. Useful if you've already
  addressed all the comments and don't want to see them anymore.
• Dismiss all Sourcery reviews: Comment @sourcery-ai dismiss on the pull
  request to dismiss all existing Sourcery reviews. Especially useful if you
  want to start fresh with a new review - don't forget to comment
  @sourcery-ai review to trigger a new review!

Customizing Your Experience

Access your dashboard to:

• Enable or disable review features such as the Sourcery-generated pull request
  summary, the reviewer's guide, and others.
• Change the review language.
• Add, remove or edit custom review instructions.
• Adjust other review settings.

Getting Help

• Contact our support team for questions or feedback.
• Visit our documentation for detailed guides and information.
• Keep in touch with the Sourcery team by following us on X/Twitter, LinkedIn or GitHub.