Fallback to empty User instead of crashing if the fetched User is not in DB #5998
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.



🎯 Goal
Instead of crashing when we try to fetch a
Userthat is not yet inserted into the DB, return an emptyUser(User(id = userId)). Note: This just covers the case where a User is transitively fetched by related operations (ex.selectMessage,selectChannel), the regularrepository.selectUser()is not affected.🛠 Implementation details
requireNotNulland instead fallback to empty User🎨 UI Changes
NA
🧪 Testing
Not really reproducible on the Sample app, however it was reported by a customer who use the
Repositoryindependently from the UI SDK.