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

feat(go-sdk)!: remove StoreId from API client config #359

Merged
merged 4 commits into from
May 23, 2024

Conversation

jimmyjames
Copy link
Contributor

Description

⚠️ Breaking change ⚠️

Removes the StoreId from the API client, and instead accept the StoreId as a parameter. As discussed in #118, this allows for the removal of the custom patch. A follow-on PR will enable overriding the StoreId per request as we do for the AuthorizationModelId.

If using api_open_fga.go directly, you will now need to pass the StoreId parameter.

References

#118

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

@jimmyjames
Copy link
Contributor Author

java-sdk test failures are not related to this change; #361 to fix

@jimmyjames jimmyjames marked this pull request as ready for review May 21, 2024 20:25
@jimmyjames jimmyjames requested a review from a team as a code owner May 21, 2024 20:25
ewanharris
ewanharris previously approved these changes May 22, 2024
@jimmyjames jimmyjames added this pull request to the merge queue May 23, 2024
Merged via the queue into main with commit 0e1aca8 May 23, 2024
15 checks passed
@jimmyjames jimmyjames deleted the remove-store-id-config branch May 23, 2024 15:53
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.

3 participants