feat: move to folder [WPB-14627] #3787
Conversation
echoes-hq
bot
added
the
echoes: product-roadmap
| } | ||
|
|
||
| @Composable | ||
| private fun Content( |
There was a problem hiding this comment.
suggestion: I would prefer to have "content" composables without injections nor viewmodels so that previews can be created more easier, would it be complicated to move these viewmodel injections up to the ConversationFoldersScreen? 🤔
| val args = remember { | ||
| navigator.navController.currentBackStackEntry?.let { | ||
| ConversationFoldersScreenDestination.argsFrom(it) | ||
| } | ||
| } |
There was a problem hiding this comment.
suggestion: for destination composables you can get args more easily by just adding it as a parameter:
@Composable
fun ConversationFoldersScreen(
args: ConversationFoldersNavArgs,
navigator: Navigator,
resultNavigator: ResultBackNavigator<ConversationFoldersNavBackArgs>,
)
| val resources = LocalContext.current.resources | ||
| val context = LocalContext.current | ||
|
|
||
| LaunchedEffect(Unit) { |
There was a problem hiding this comment.
Should we use lifecycle.repeatOnLifecycle() here to collect only when app is in foreground?
There was a problem hiding this comment.
I think is unnecessary because even if user goes to background after triggering action it should close select folder screen either way
| private val moveConversationToFolder: MoveConversationToFolderUseCase, | ||
| ) : MoveConversationToFolderVM, ViewModel() { | ||
|
|
||
| var state: MoveConversationToFolderState by mutableStateOf(MoveConversationToFolderState()) |
There was a problem hiding this comment.
Should this be private? Or keep it public with private get() and then actionableState() is not needed.
|
PR Submission Checklist for internal contributors
The PR Title
SQPIT-764The PR Description
What's new in this PR?
Attachments (Optional)
screen-20250107-095349.mp4