Release v2.2.0#1109
Conversation
Prevent duplicate reply submissions
Fix UI clipping on Withdraw screen for large text sizes
Fix FolderCreateScreen based on QA
My Folder Screen UI based on QA
Update post comment empty state in PostScreen
Update Bottom sheet style
Feed UI based on Design QA
Settings UI based on Design QA
|
Important Review skippedAuto reviews are disabled on base/target branches other than the default branch. Please check the settings in the CodeRabbit UI or the ⚙️ Run configurationConfiguration used: Organization UI Review profile: ASSERTIVE Plan: Pro Run ID: You can disable this status message by setting the Use the checkbox below for a quick retry:
✨ Finishing Touches🧪 Generate unit tests (beta)
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
![chatgpt-codex-connector[bot]](https://avatars.githubusercontent.com/in/1144995?s=60&v=4){kind=small}
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: fd6fdd0b9e
ℹ️ About Codex in GitHub
Codex has been enabled to automatically review pull requests in this repo. Reviews are triggered when you
- Open a pull request for review
- Mark a draft as ready
- Comment "@codex review".
If Codex has suggestions, it will comment; otherwise it will react with 👍.
When you sign up for Codex through ChatGPT, Codex can also answer questions or update the PR, like "@codex address that feedback".
| private val _postCommentCreateState = MutableLiveData<Resource<Boolean>>() | ||
| val postCommentCreateState: LiveData<Resource<Boolean>> get() = _postCommentCreateState |
There was a problem hiding this comment.
This replaces the previous Event<Boolean> with sticky LiveData<Resource<Boolean>>, but both PostScreen and CommentBottomSheetDialog handle any existing value as soon as they observe it. After a comment send fails, reopening a comments sheet or recreating the screen immediately replays the old ERROR and shows the network-error snackbar before the user does anything; after a prior success it also triggers an extra requestPostComment(postId) for the next opened post. Keep this as a one-shot event/SharedFlow or clear the state after the UI handles it.
Useful? React with 👍 / 👎.
2 participants
No description provided.