Skip to content

feat: do not allow renaming file with extension (WPB-18314) #4114

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

Open
wants to merge 1 commit into
base: develop
Choose a base branch
from

Conversation

ohassine
Copy link
Member


PR Submission Checklist for internal contributors

  • The PR Title

    • conforms to the style of semantic commits messages¹ supported in Wire's Github Workflow²
    • contains a reference JIRA issue number like SQPIT-764
    • answers the question: If merged, this PR will: ... ³
  • The PR Description

    • is free of optional paragraphs and you have filled the relevant parts to the best of your ability

What's new in this PR?

Issues

  • Hide extension from name while renaming a file
  • Do not allow to use "." and "/" while renaming

Testing

Test Coverage (Optional)

  • I have added automated test to this contribution

How to Test

Briefly describe how this change was tested and if applicable the exact steps taken to verify that it works as expected.

Notes (Optional)

Specify here any other facts that you think are important for this issue.

Attachments (Optional)

Attachments like images, videos, etc. (drag and drop in the text box)


PR Post Submission Checklist for internal contributors (Optional)

  • Wire's Github Workflow has automatically linked the PR to a JIRA issue

PR Post Merge Checklist for internal contributors

  • If any soft of configuration variable was introduced by this PR, it has been added to the relevant documents and the CI jobs have been updated.

References
  1. https://sparkbox.com/foundry/semantic_commit_messages
  2. https://github.com/wireapp/.github#usage
  3. E.g. feat(conversation-list): Sort conversations by most emojis in the title #SQPIT-764.

@ohassine ohassine changed the title feat: do not allow renaming file with extension feat: do not allow renaming file with extension (WPB-18314) Jul 15, 2025
@ohassine ohassine requested review from yamilmedina and Garzas July 15, 2025 07:37
Copy link

Copy link
Contributor

@yamilmedina yamilmedina left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM ! Just a question to understand better the need of the change in renameNodeViewModel, as it seems not necessary at all to pass the argument to the function to rename.

@@ -91,7 +91,7 @@ fun RenameNodeScreen(
) {
WirePrimaryButton(
text = stringResource(R.string.rename_label),
onClick = { renameNodeViewModel.renameNode() },
onClick = { renameNodeViewModel.renameNode(renameNodeViewModel.textState.text.toString()) },
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Question: Why do we need to pass the reference ? Since we could just access it from within the viewmodel, like it was before ? 🤔


advanceUntilIdle()
viewModel.actions.test {
with(expectMostRecentItem()) {
assertEquals(false, viewModel.displayNameState.loading)
assertEquals(DisplayNameState.Completed.Success, viewModel.displayNameState.completed)
assertTrue(this is RenameNodeViewModelAction.Success)
coVerify(exactly = 1) { arrangement.renameNodeUseCase(eq(UUID), eq(CURRENT_PATH), eq("newFileName.txt")) }
}
}
}

@Test
fun `given renameNodeUseCase failure, when rename is called, then send failure action`() = runTest {
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Can we also have test for InvalidNameError

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants