Skip to content

Conversation

@Antreesy
Copy link
Contributor

@Antreesy Antreesy commented Nov 24, 2025

☑️ Resolves

🖌️ UI Checklist

🖼️ Screenshots / Screencasts

2025-11-24_14h54_47

🚧 Tasks

  • API - missing $metaData[Message::METADATA_SILENT] for call_started system message
  • API - some additional messages to add via HPB?
  • Frontend - call_ended has too many backend information to copy mechanism on client

🏁 Checklist

  • 🌏 Tested with different browsers / clients:
    • Chromium (Chrome / Edge / Opera / Brave)
    • Firefox
    • Safari
    • Talk Desktop
    • Integrations with Files sidebar and other apps
    • 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

}

chatStore.processChatBlocks(token, [message], { mergeBy: chatStore.getLastKnownId(token) })
store.dispatch('processMessage', { token, message })
Copy link
Contributor

Choose a reason for hiding this comment

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

There two bonuses to process:

  • Poll sys messages now include additional information
  • Thread object is included in thread-created sys message

Do you want me to do it?

Copy link
Contributor Author

@Antreesy Antreesy Nov 24, 2025

Choose a reason for hiding this comment

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

Of course, but it can be in processMessage as separate PR, like reactions PR I recently sent

@Antreesy Antreesy force-pushed the fix/noid/chat-relay-translations branch 2 times, most recently from 82edea4 to 53e5ba9 Compare December 22, 2025 17:27
@Antreesy Antreesy force-pushed the fix/noid/chat-relay-translations branch from 53e5ba9 to 8e88ae6 Compare December 23, 2025 13:33
@Antreesy Antreesy changed the base branch from main to fix/noid/chat-relay-prereq December 23, 2025 13:33
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants