Skip to content

Conversation

@Siddhant-K-code
Copy link
Member

@Siddhant-K-code Siddhant-K-code commented Jul 12, 2025

Documentation update from v1.8.15 → v1.9.0

Related #1054

Summary by CodeRabbit

  • Documentation
    • Updated configuration documentation to reflect OpenFGA version 1.9.0.
    • Added and reorganized configuration options, including new secondary datastore and iterator cache settings.
    • Updated default values and improved clarity in option descriptions.

- Update configuration documentation to reference v1.8.15
- Update resolveNodeBreadthLimit default value from 100 to 10
- Update dependencies to latest versions
- Update configuration documentation to reference v1.9.0
- Update schema reference links to point to v1.9.0 release
@Siddhant-K-code Siddhant-K-code requested review from a team as code owners July 12, 2025 07:02
@coderabbitai
Copy link
Contributor

coderabbitai bot commented Jul 12, 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 documentation for OpenFGA's configuration was updated to version 1.9.0, with new and reorganized configuration options, including secondary datastore parameters and iterator cache settings. Dependency versions in package.json were also updated, primarily for Docusaurus, OpenFGA SDK, and related packages, without changes to code or exports.

Changes

File(s) Change Summary
docs/content/getting-started/setup-openfga/configuration.mdx Updated OpenFGA config documentation to v1.9.0; added secondary datastore and iterator cache options; reorganized throttling settings; updated links and defaults.
package.json Upgraded Docusaurus, OpenFGA SDK, and other dependencies; no changes to scripts or public interfaces.

Sequence Diagram(s)

sequenceDiagram
    participant User
    participant Documentation
    User ->> Documentation: Reads configuration options
    Documentation -->> User: Presents updated options (v1.9.0)
    User ->> Documentation: Looks for datastore and caching settings
    Documentation -->> User: Shows new secondary datastore and iterator cache configs
Loading

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 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.

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 f9a0151 and c695014.

⛔ Files ignored due to path filters (1)
  • package-lock.json is excluded by !**/package-lock.json
📒 Files selected for processing (2)
  • docs/content/getting-started/setup-openfga/configuration.mdx (4 hunks)
  • package.json (2 hunks)
⏰ Context from checks skipped due to timeout of 90000ms. You can increase the timeout in your CodeRabbit configuration to a maximum of 15 minutes (900000ms). (6)
  • GitHub Check: deploy-preview
  • GitHub Check: Test deployment
  • GitHub Check: markdown-link-check
  • GitHub Check: Run Checks
  • GitHub Check: markdown-link-check-md
  • GitHub Check: Socket Security: Pull Request Alerts
🔇 Additional comments (5)
package.json (2)

28-32: Confirm Docusaurus 3.8.1 requirements & breaking-change notes

@docusaurus/* was bumped from 3.7.0 → 3.8.1.
The minor bump may introduce peer-dependency or Node-engine shifts (e.g. minimum Node 18). Please confirm the docs site still builds in CI and locally after this upgrade.


56-57: Major ESLint jump – ensure config compatibility

eslint jumped 8 → 9. This is a semver-major release; many core rules were renamed/removed and the default parser options changed. Run npm run lint locally and in CI to catch any rule breakage or phantom errors, and upgrade shareable configs/plugins if needed (eslint-plugin-react@7 is still compatible but double-check).

docs/content/getting-started/setup-openfga/configuration.mdx (3)

119-119: Default reduced from 100 → 10 – double-check source code

resolveNodeBreadthLimit default is now documented as 10. Verify the server actually ships with this new default; otherwise the doc will mislead users.


137-141: Secondary datastore options look good

Nice addition of secondaryUri, secondaryUsername, and secondaryPassword; the Env-Var and flag names follow the existing pattern.


191-197: Iterator-cache options added – wording matches Check cache

The new listObjectsIteratorCache.* rows are clear and consistent.

| `listUsersDispatchThrottling.frequency` | <div id="OPENFGA_LIST_USERS_DISPATCH_THROTTLING_FREQUENCY"><code>OPENFGA_LIST_USERS_DISPATCH_THROTTLING_FREQUENCY</code></div> | `list-users-dispatch-throttling-frequency` | string (duration) | the frequency period that the deprioritized throttling queue is evaluated for a list users request. A higher value will result in more aggressive throttling | `10µs` |
| `listUsersDispatchThrottling.threshold` | <div id="OPENFGA_LIST_USERS_DISPATCH_THROTTLING_THRESHOLD"><code>OPENFGA_LIST_USERS_DISPATCH_THROTTLING_THRESHOLD</code></div> | `list-users-dispatch-throttling-threshold` | integer | define the number of recursive operations to occur before getting throttled for a list users request | `100` |
| `listUsersDispatchThrottling.maxThreshold` | <div id="OPENFGA_LIST_USERS_DISPATCH_THROTTLING_MAX_THRESHOLD"><code>OPENFGA_LIST_USERS_DISPATCH_THROTTLING_MAX_THRESHOLD</code></div> | `list-users-dispatch-throttling-max-threshold` | integer | define the maximum dispatch threshold beyond above which requests will be throttled for a list users request. 0 will use the 'dispatchThrottling.threshold' value as maximum | `0` |
| `sharedIterator` | | `` | | | |
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

sharedIterator row is blank – fill in or remove

The table entry for sharedIterator has no Env Var, flag, type, description, or default. Either supply the missing details or drop the row to avoid confusing readers.

-| `sharedIterator` |  | `` |  |  |  |
+| `sharedIterator.enabled` | <div id="OPENFGA_SHARED_ITERATOR_ENABLED"><code>OPENFGA_SHARED_ITERATOR_ENABLED</code></div> | `shared-iterator-enabled` | boolean | (add description here) | `false` |
📝 Committable suggestion

‼️ IMPORTANT
Carefully review the code before committing. Ensure that it accurately replaces the highlighted code, contains no missing lines, and has no issues with indentation. Thoroughly test & benchmark the code to ensure it meets the requirements.

Suggested change
| `sharedIterator` | | `` | | | |
-| `sharedIterator` | | `` | | | |
+| `sharedIterator.enabled` | <div id="OPENFGA_SHARED_ITERATOR_ENABLED"><code>OPENFGA_SHARED_ITERATOR_ENABLED</code></div> | `shared-iterator-enabled` | boolean | (add description here) | `false` |
🤖 Prompt for AI Agents
In docs/content/getting-started/setup-openfga/configuration.mdx at line 202, the
table row for `sharedIterator` is completely blank with no environment variable,
flag, type, description, or default value. Either fill in all the missing
details for `sharedIterator` to provide complete information or remove the
entire row from the table to prevent confusion for readers.

@rhamzeh
Copy link
Member

rhamzeh commented Jul 14, 2025

Hey @Siddhant-K-code! Thanks for splitting it out!

Can you make sure to update the eslint config so that the tests pass?

Copy link
Member

@rhamzeh rhamzeh left a comment

Choose a reason for hiding this comment

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

Can you remove the unrelated parts from this PR?

@Siddhant-K-code Siddhant-K-code requested a review from rhamzeh July 15, 2025 09:32
@Siddhant-K-code
Copy link
Member Author

Siddhant-K-code commented Jul 15, 2025

@rhamzeh, Lint checks are failing due to unrelated changes 👀

image

We need to update link or remove the following section:

https://github.com/Siddhant-K-code/openfga.dev/blob/docs/update-openfga-v1.9.0/blog/fine-grained-news-2024-03.md?plain=1#L52

@rhamzeh
Copy link
Member

rhamzeh commented Jul 15, 2025

That's OK I fixed that in your other PR

@rhamzeh rhamzeh closed this Sep 4, 2025
@Siddhant-K-code Siddhant-K-code deleted the docs/update-openfga-v1.9.0 branch October 25, 2025 16:19
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.

2 participants