Skip to content
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.

Sign up for GitHub

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

fix: add the link to config schema for tuples in transactional writes and support it to by default info #937

Open
wants to merge 1 commit into
base: main
Choose a base branch
from
Open

fix: add the link to config schema for tuples in transactional writes and support it to by default info #937

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion docs/content/interacting/transactional-writes.mdx
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -167,7 +167,7 @@ curl -X POST 'http://localhost:8080/stores/{store_id}/write' \

</details>

The Write API allows you to send up to 100 unique tuples in the request. (This limit applies to the sum of both writes and deletes in that request). This means we can submit one API call that converts the `tweet` from public to visible to only the `user`'s followers.
The Write API allows you to send up to 100 unique tuples by default and can be configured in the request as you can refer from this <link>(https://github.com/openfga/openfga/blob/main/.config-schema.json#L3-L7) to the config schema. (This limit applies to the sum of both writes and deletes in that request). This means we can submit one API call that converts the `tweet` from public to visible to only the `user`'s followers.

<WriteRequestViewer
relationshipTuples={[
Expand Down