Skip to content

_ #206

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

Merged
merged 3 commits into from
Jul 4, 2025
Merged

_ #206

merged 3 commits into from
Jul 4, 2025

Conversation

xtsea
Copy link
Contributor

@xtsea xtsea commented Jul 4, 2025

Summary by Sourcery

Update README link for API key instructions and adjust HTTP status error handling flag.

Bug Fixes:

  • Change AsyncStatusError invocation to disable httpx-specific status checking.

Documentation:

  • Correct the API key retrieval documentation link in README to point to the proper section.

Copy link
Contributor

sourcery-ai bot commented Jul 4, 2025

Reviewer's Guide

This PR corrects the documentation link for obtaining the API key in the README and adjusts the HTTP status error handling flag in the asynchronous client.

Sequence diagram for updated HTTP status error handling in post()

sequenceDiagram
    participant Client as _client.py
    participant HTTPX as HTTPX
    participant AsyncStatusError as AsyncStatusError
    Client->>HTTPX: Send POST request
    HTTPX-->>Client: Return response (resp)
    Client->>AsyncStatusError: await AsyncStatusError(resp, status_httpx=False)
    AsyncStatusError-->>Client: (error handling)
    Client->>HTTPX: resp.raise_for_status()
    alt use_type == ResponseType.IMAGE
        Client->>HTTPX: await resp.read()
    else
        Client->>HTTPX: await resp.json()
    end
Loading

File-Level Changes

Change Details Files
Fixed API key link in documentation
  • Updated the URL fragment for the API key retrieval section
README.md
Adjusted error handling behavior in async client
  • Changed AsyncStatusError invocation to use status_httpx=False
Ryzenth/_client.py

Tips and commands

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

@xtsea xtsea merged commit 5911f6c into beta Jul 4, 2025
3 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant