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.

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: correct flag value type in delete, import, and write #389

Merged
merged 2 commits into from
Sep 9, 2024

Conversation

ewanharris
Copy link
Member

Description

Overlooked the need to change the flag declaration as part of the refactoring here #382.

Will work on adding some integration tests to cover this.

References

Fixes #387

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

@ewanharris ewanharris requested a review from a team as a code owner September 9, 2024 07:46
@ewanharris ewanharris force-pushed the fix/correct-type-on-max-tuples-and-requests branch from 8bf614b to dc43c71 Compare September 9, 2024 08:27
cmd/tuple/import.go Outdated Show resolved Hide resolved
rhamzeh
rhamzeh previously approved these changes Sep 9, 2024
@ewanharris ewanharris added this pull request to the merge queue Sep 9, 2024
Merged via the queue into main with commit 52c4302 Sep 9, 2024
16 checks passed
@ewanharris ewanharris deleted the fix/correct-type-on-max-tuples-and-requests branch September 9, 2024 11:32
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.

fga tuple write returns an error
3 participants