Skip to content
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

fix: user contacts menu instead of conversation participants (there c… #14143

Open
wants to merge 3 commits into
base: main
Choose a base branch
from

Conversation

DorraJaouad
Copy link
Contributor

@DorraJaouad DorraJaouad commented Jan 16, 2025

☑️ Resolves

  • Missing items navigation
  • Correct list of contacts rather conversation participants (some users might have left and they have messages)
  • Trigger re-fetch after removing filter chips
  • Types syntax

🖌️ UI Checklist

🖼️ Screenshots / Screencasts

Recording.2025-01-16.200647.mp4

🏁 Checklist

  • 🌏 Tested with different browsers / clients:
    • Chromium (Chrome / Edge / Opera / Brave)
    • Firefox
    • Safari
    • Talk Desktop
    • Not risky to browser differences / client
  • 🖌️ Design was reviewed, approved or inspired by the design team
  • ⛑️ Tests are included or not possible
  • 📗 User documentation in https://github.com/nextcloud/documentation/tree/master/user_manual/talk has been updated or is not required
    …ould be users who left)

@DorraJaouad DorraJaouad added this to the 🌿 Next Beta (31) milestone Jan 16, 2025
@DorraJaouad DorraJaouad requested a review from Antreesy January 16, 2025 19:15
@DorraJaouad DorraJaouad self-assigned this Jan 16, 2025
*/
async function fetchContacts(searchTerm: string = '') {
try {
const { data: { contacts } } = await getContacts(searchTerm)
Copy link
Member

Choose a reason for hiding this comment

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

Ah, this is what Maksim had asked me. Hmm using contacts is quite bad for multiple reasons:

  1. It's limited by share restrictions, so you might not even see everyone that is in the room
  2. Guests, federated users, emails, … are not supported

I would stay with the current participants for now. As a follow up I would then as a replacement create a new API endpoint which provides the information that you need for all message authors instead?

Copy link
Contributor

Choose a reason for hiding this comment

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

Better to do it together with messages/search endpoint then, since UnifiedSearch provider is also blocking guests, federated users, e.t.c

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