docs: remove fga_client.close() from README (#191)

[JsMelix]

Description

Removes the unnecessary fga_client.close() call from the README example.

What problem is being solved?

The example included a .close() call, but the Python SDK automatically handles client closing via context managers, so users don't need to call it manually.

How is it being solved?

By removing the redundant line from the README documentation.

What changes are made to solve it?

• Updated README.md
• Improved example clarity

References

Closes #191

Review Checklist

• I have clicked on "allow edits by maintainers"
• The correct base branch is being used (main)
• I have updated documentation

---

🟣 Hacktoberfest
This PR is part of Hacktoberfest 2025 🎃.
If valid, please mark it as hacktoberfest-accepted. Thank you!

Summary by CodeRabbit

• Refactor
  • Improved resource cleanup handling by streamlining internal management processes.

[linux-foundation-easycla]

The committers listed above are authorized under a signed CLA.

• ✅ login: SoulPancake / name: Anurag Bandyopadhyay (8ce1e05)

[coderabbitai]

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 README.md was updated to remove redundant explicit await fga_client.close() calls from three async context manager examples, allowing the context manager's automatic cleanup mechanism to handle resource deallocation.

Changes

Cohort / File(s)	Summary
Documentation cleanup README.md	Removed explicit await fga_client.close() statements from three async with OpenFgaClient(...) code examples to eliminate redundant resource cleanup calls.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~3 minutes

Pre-merge checks and finishing touches

✅ Passed checks (5 passed)

Check name	Status	Explanation
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.
Title Check	✅ Passed	The PR title "docs: remove fga_client.close() from README (#191)" is concise, specific, and directly related to the main change described in the raw_summary. The title clearly communicates that the PR removes explicit close calls from the README examples, which is exactly what the changeset accomplishes. The title uses appropriate prefixing ("docs:") to indicate it's a documentation change and includes the issue number for reference, making it clear and actionable for developers scanning the history.
Linked Issues Check	✅ Passed	The PR directly addresses the objective from issue #191 by removing explicit fga_client.close() calls from the README examples within async-with blocks. The raw_summary confirms that the changes align with the issue's requirement to eliminate redundant manual close calls since context managers (with __aexit__() and __exit__() methods) already handle resource cleanup automatically. The PR fully satisfies the coding requirement specified in the linked issue without introducing unrelated changes.
Out of Scope Changes Check	✅ Passed	The PR introduces only in-scope changes focused entirely on addressing issue #191. The raw_summary indicates that only README.md was modified, with changes limited to removing explicit close calls from async-with block examples. No unrelated modifications, refactoring, or feature additions are present. The changes are directly tied to the documented objective of improving README example clarity by removing unnecessary manual close calls.
Docstring Coverage	✅ Passed	No functions found in the changes. Docstring coverage check skipped.

Tip

📝 Customizable high-level summaries are now available in beta!

You can now customize how CodeRabbit generates the high-level summary in your pull requests — including its content, structure, tone, and formatting.

• Provide your own instructions using the high_level_summary_instructions setting.
• Format the summary however you like (bullet lists, tables, multi-section layouts, contributor stats, etc.).
• Use high_level_summary_in_walkthrough to move the summary from the description to the walkthrough section.

Example instruction:

"Divide the high-level summary into five sections:

1. 📝 Description — Summarize the main change in 50–60 words, explaining what was done.
2. 📓 References — List relevant issues, discussions, documentation, or related PRs.
3. 📦 Dependencies & Requirements — Mention any new/updated dependencies, environment variable changes, or configuration updates.
4. 📊 Contributor Summary — Include a Markdown table showing contributions:
   | Contributor | Lines Added | Lines Removed | Files Changed |
5. ✔️ Additional Notes — Add any extra reviewer context.
   Keep each section concise (under 200 words) and use bullet or numbered lists for clarity."

Note: This feature is currently in beta for Pro-tier users, and pricing will be announced later.

---

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

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands and usage tips.}