Merged
Conversation
When "Enforce referential integrity for memberships" then when setting restriction(channelMembers) we need to make sure that both channel and user exist in AppContext.
marcin-cebo
requested review from
jguz-pubnub and
wkal-pubnub
as code owners
wkal-pubnub
approved these changes
Feb 20, 2025
Contributor
Author
|
@pubnub-release-bot release kotlin as 0.11.1 |
Contributor
|
🚀 Release successfully completed 🚀 |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
fix: Fixed bug related to setting user restriction
The issue occurred when "Enforce referential integrity for memberships" was enabled and a user did not exist in AppContext.