Skip to content

chore: update readme import error #202

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 2 commits into from
Jul 30, 2025
Merged

chore: update readme import error #202

merged 2 commits into from
Jul 30, 2025

Conversation

carlastabile
Copy link
Contributor

@carlastabile carlastabile commented Jul 24, 2025

Fixing outdated README import

Description

What problem is being solved?

Update README

How is it being solved?

Adding correct import location

What changes are made to solve it?

References

Review Checklist

  • I have clicked on "allow edits by maintainers".
  • I have added documentation for new/changed functionality in this PR or in a PR to openfga.dev [Provide a link to any relevant PRs in the references section above]
  • The correct base branch is being used, if not main
  • I have added tests to validate that the change in functionality is working as expected

Summary by CodeRabbit

  • Documentation
    • Updated the import paths in the "List Users" example section of the README for improved clarity.

@carlastabile carlastabile requested review from a team as code owners July 24, 2025 12:07
Copy link
Contributor

coderabbitai bot commented Jul 24, 2025

Important

Review skipped

Auto incremental reviews are disabled on this repository.

Please check the settings in the CodeRabbit UI or the .coderabbit.yaml file in this repository. To trigger a single review, invoke the @coderabbitai review command.

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

Walkthrough

The import paths for ClientListUsersRequest and ClientTuple in the "List Users" example section of the README were updated to reference a more specific submodule. No usage or functional changes were made to the example code.

Changes

File(s) Change Summary
README.md Updated import statements in the "List Users" example to use a more specific submodule path for ClientListUsersRequest and ClientTuple.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~2 minutes

✨ Finishing Touches
🧪 Generate unit tests
  • Create PR with unit tests
  • Post copyable unit tests in a comment
  • Commit unit tests in branch chore/update-readme

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share
🪧 Tips

Chat

There are 3 ways to chat with CodeRabbit:

  • Review comments: Directly reply to a review comment made by CodeRabbit. Example:
    • I pushed a fix in commit <commit_id>, please review it.
    • Explain this complex logic.
    • Open a follow-up GitHub issue for this discussion.
  • Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query. Examples:
    • @coderabbitai explain this code block.
    • @coderabbitai modularize this function.
  • PR comments: Tag @coderabbitai in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
    • @coderabbitai gather interesting stats about this repository and render them as a table. Additionally, render a pie chart showing the language distribution in the codebase.
    • @coderabbitai read src/utils.ts and explain its main purpose.
    • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.
    • @coderabbitai help me debug CodeRabbit configuration file.

Support

Need help? Create a ticket on our support page for assistance with any issues or questions.

Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments.

CodeRabbit Commands (Invoked using PR comments)

  • @coderabbitai pause to pause the reviews on a PR.
  • @coderabbitai resume to resume the paused reviews.
  • @coderabbitai review to trigger an incremental review. This is useful when automatic reviews are disabled for the repository.
  • @coderabbitai full review to do a full review from scratch and review all the files again.
  • @coderabbitai summary to regenerate the summary of the PR.
  • @coderabbitai generate docstrings to generate docstrings for this PR.
  • @coderabbitai generate sequence diagram to generate a sequence diagram of the changes in this PR.
  • @coderabbitai generate unit tests to generate unit tests for this PR.
  • @coderabbitai resolve resolve all the CodeRabbit review comments.
  • @coderabbitai configuration to show the current CodeRabbit configuration for the repository.
  • @coderabbitai help to get help.

Other keywords and placeholders

  • Add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.
  • Add @coderabbitai summary to generate the high-level summary at a specific location in the PR description.
  • Add @coderabbitai anywhere in the PR title to generate the title automatically.

CodeRabbit Configuration File (.coderabbit.yaml)

  • You can programmatically configure CodeRabbit by adding a .coderabbit.yaml file to the root of your repository.
  • Please see the configuration documentation for more information.
  • If your editor has YAML language server enabled, you can add the path at the top of this file to enable auto-completion and validation: # yaml-language-server: $schema=https://coderabbit.ai/integrations/schema.v2.json

Documentation and Community

  • Visit our Documentation for detailed information on how to use CodeRabbit.
  • Join our Discord Community to get help, request features, and share feedback.
  • Follow us on X/Twitter for updates and announcements.

@codecov-commenter
Copy link

codecov-commenter commented Jul 24, 2025

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 70.68%. Comparing base (c87c8d2) to head (356fb5e).

❌ Your project status has failed because the head coverage (70.68%) is below the target coverage (80.00%). You can increase the head coverage or adjust the target coverage.

Additional details and impacted files
@@           Coverage Diff           @@
##             main     #202   +/-   ##
=======================================
  Coverage   70.68%   70.68%           
=======================================
  Files         134      134           
  Lines       10870    10870           
=======================================
  Hits         7683     7683           
  Misses       3187     3187           

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:
  • ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.

Copy link
Contributor

@coderabbitai coderabbitai bot left a comment

Choose a reason for hiding this comment

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

Actionable comments posted: 1

📜 Review details

Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between c87c8d2 and 59ac01c.

📒 Files selected for processing (1)
  • README.md (1 hunks)

README.md Outdated
Comment on lines 1063 to 1064
from openfga_sdk.client.models.list_users_request import ClientListUsersRequest, ClientTuple

Copy link
Contributor

Choose a reason for hiding this comment

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

⚠️ Potential issue

Incorrect module referenced for ClientTuple

ClientTuple is defined in its own module (client_tuple.py) and is re-exported by openfga_sdk.client.models, but it is not part of list_users_request.py.
The new import therefore fails at runtime / copy-paste:

>>> from openfga_sdk.client.models.list_users_request import ClientTuple
ImportError: cannot import name 'ClientTuple' ...

Fix the example to import each symbol from its correct module (or from the package init that already re-exports both):

-from openfga_sdk.client.models.list_users_request import ClientListUsersRequest, ClientTuple
+from openfga_sdk.client.models.list_users_request import ClientListUsersRequest
+from openfga_sdk.client.models import ClientTuple

This keeps ClientListUsersRequest narrowed to its own file while maintaining the valid path for ClientTuple.
Please adjust before merging to avoid propagating a faulty README example.

🤖 Prompt for AI Agents
In README.md around lines 1063 to 1064, the import statement incorrectly imports
ClientTuple from list_users_request.py where it is not defined, causing runtime
import errors. Update the import to get ClientTuple from its correct module
client_tuple.py or from the package init that re-exports both
ClientListUsersRequest and ClientTuple, ensuring each symbol is imported from
its proper source to fix the import error.

@carlastabile carlastabile added the documentation Improvements or additions to documentation label Jul 24, 2025
Copy link
Member

@evansims evansims left a comment

Choose a reason for hiding this comment

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

Thanks so much, @carlastabile! Appreciate it

@evansims evansims added this pull request to the merge queue Jul 30, 2025
Merged via the queue into main with commit d675336 Jul 30, 2025
28 checks passed
@evansims evansims deleted the chore/update-readme branch July 30, 2025 16:03
@coderabbitai coderabbitai bot mentioned this pull request Jul 30, 2025
4 tasks
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
documentation Improvements or additions to documentation
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants