feat: Make possible to report a thread or message as phishing from spam folder

[solrubado]

No description provided.

[Copilot]

Pull request overview

Enables reporting a thread/message as phishing even when it originates from the Spam folder.

Changes:

• Always display the “Phishing” action item (including in Spam).
• Attempt to reset multi-select mode when phishing report completes (currently implemented in a way that closes multi-select too early).

Reviewed changes

Copilot reviewed 2 out of 2 changed files in this pull request and generated no comments.

File	Description
app/src/main/java/com/infomaniak/mail/ui/main/thread/actions/ThreadActionsBottomSheetDialog.kt	Makes phishing action always visible; adds multi-select reset tied to phishing result observer setup.
app/src/main/java/com/infomaniak/mail/ui/main/thread/actions/MultiSelectBottomSheetDialog.kt	Adds multi-select reset tied to phishing result observer setup.

Comments suppressed due to low confidence (2)

app/src/main/java/com/infomaniak/mail/ui/main/thread/actions/MultiSelectBottomSheetDialog.kt:261

• mainViewModel.isMultiSelectOn = false is set when registering the reportPhishingTrigger observer (called from onViewCreated), so simply opening this bottom sheet will immediately exit multi-select mode. This is very likely unintended; instead, set isMultiSelectOn = false only when the phishing action completes (inside the observe { ... } callback) or when the user confirms the phishing report.

    private fun observeReportPhishingResult() {
        mainViewModel.isMultiSelectOn = false
        mainViewModel.reportPhishingTrigger.observe(viewLifecycleOwner) {
            descriptionDialog.resetLoadingAndDismiss()
            findNavController().popBackStack()
        }

app/src/main/java/com/infomaniak/mail/ui/main/thread/actions/ThreadActionsBottomSheetDialog.kt:140

• mainViewModel.isMultiSelectOn = false is executed as soon as the observer is set up (on bottom sheet creation), which will close multi-select even if the user hasn’t reported phishing. This changes UI state just by opening the dialog. Move the assignment into the reportPhishingTrigger.observe { ... } block (and/or guard it with shouldCloseMultiSelection) so multi-select is only closed when the phishing flow completes.

    private fun observeReportPhishingResult() {
        mainViewModel.isMultiSelectOn = false
        mainViewModel.reportPhishingTrigger.observe(viewLifecycleOwner) {
            descriptionDialog.resetLoadingAndDismiss()
            findNavController().popBackStack()
        }

---

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

[Copilot]

Pull request overview

Copilot reviewed 2 out of 2 changed files in this pull request and generated 2 comments.

---

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

[Copilot]

Pull request overview

Copilot reviewed 3 out of 3 changed files in this pull request and generated 1 comment.

---

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud