Skip to content

Conversation

@jullianm
Copy link
Contributor

WPB-23032

Issue

This PR fixe an issue where, in the shared "Drive" tab, we don't display the conversation name the file was shared in.
It also takes this opportunity to do some preparation work for the sorting & filtering feature coming up (filtering by conversations and participants)

Simulator.Screen.Recording.-.Snapshots.-.2026-01-23.at.15.45.49.mov

Testing

go to shared "Drive" tab, the subtitle of the cell should display the file owner and the conversation name it's linked (i.e "userA in conversationB")
conversation files list should remain unchanged

Checklist

  • Title contains a reference JIRA issue number like [WPB-XXX].
  • Description is filled and free of optional paragraphs.
  • Adds/updates automated tests.

UI accessibility checklist

If your PR includes UI changes, please utilize this checklist:

  • Make sure you use the API for UI elements that support large fonts.
  • All colors are taken from WireDesign.ColorTheme or constructed using WireDesign.BaseColorPalette.
  • New UI elements have Accessibility strings for VoiceOver.

@github-actions
Copy link
Contributor

github-actions bot commented Jan 23, 2026

Test Results

  2 files  185 suites   2m 6s ⏱️
730 tests 729 ✅ 0 💤 1 ❌
731 runs  730 ✅ 0 💤 1 ❌

For more details on these failures, see this check.

Results for commit 405c2a4.

♻️ This comment has been updated with latest results.

@jullianm jullianm enabled auto-merge January 23, 2026 16:26
Copy link
Collaborator

@WilhelmOks WilhelmOks left a comment

Choose a reason for hiding this comment

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

nice work

@datadog-wireapp
Copy link

datadog-wireapp bot commented Jan 27, 2026

⚠️ Tests

Fix all issues with Cursor

⚠️ Warnings

🧪 1 Test failed

testFilesViewItemView_dynamicTypeVariants() from WireMessagingTests.FilesViewTests (Datadog) (Fix with Cursor)
Test crashed with signal trap.

ℹ️ Info

❄️ No new flaky tests detected

This comment will be updated automatically if new data arrives.
🔗 Commit SHA: 405c2a4 | Docs | Was this helpful? Give us feedback!

@jullianm jullianm changed the base branch from develop to release/cycle-4.15 January 28, 2026 08:32
Copy link
Contributor

@samwyndham samwyndham left a comment

Choose a reason for hiding this comment

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

Nice work. Left a sanity check comment as I thought I recalled that conversation name might be part of the nodes response. Maybe something to double check with Charles if you haven't already.


/// The name of the `cell` used for Wire Drive file management.
var wireCellName: String { get }
var wireDriveName: String { get }
Copy link
Contributor

Choose a reason for hiding this comment

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

thought: I wonder if we should still use the term cell in some cases because this is what it really is? Or maybe node because I guess it is the name of the root node of the conversation. So maybe wireDriveNodeName? What do you think?

Copy link
Contributor Author

Choose a reason for hiding this comment

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

Yes you're right, I went autopilot mode here I shouldn't have renamed it. I'll fix that, probably wireDriveNodeName makes sense

return context.fetchOrAssert(request: request)
}

static func fetchDriveConversations(in context: NSManagedObjectContext) -> [ZMConversation] {
Copy link
Contributor

Choose a reason for hiding this comment

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

sanity check: Do we definitely need to do this. The conversation name isn't returned as part of the node response somewhere?

Copy link
Contributor Author

@jullianm jullianm Jan 28, 2026

Choose a reason for hiding this comment

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

No it's not, as far as I remember during the sorting & filtering refinement I asked Charles if we would get the conversation linked to the node in the response and he answered that we would need to get all conversations locally and pass their IDs to the API to filter properly (I think they don't map it on BE side). However, let me double check that because I might be wrong.

Though I think we'd still need that code as we'll need to know the participants that are part of the conversation (out of scope for this ticket but I'm kind of preparing the sorting & filtering feature too).

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants