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

[FEATURE REQ] Merge ChatThreadProperties and ChatThreadItem (sync their properties) #46314

Open
ErikAndreas opened this issue Sep 26, 2024 · 1 comment
Labels
Client This issue points to a problem in the data-plane of the library. Communication customer-reported Issues that are reported by GitHub users external to the Azure organization. needs-team-attention Workflow: This issue needs attention from Azure service team or SDK team question The issue doesn't require a change to the product in order to be resolved. Most issues start as that Service Attention Workflow: This issue is responsible by Azure service team.

Comments

@ErikAndreas
Copy link

ErikAndreas commented Sep 26, 2024

Library name

Azure.Communication.Chat

Please describe the feature.

Keeping track of your own threads (doing internal filtering/rules for which threads to display when etc) means using the ChatThreadClient (per thread) as opposed to using ChatClient.GetChatThreads (returns all threads user is participant in?)

But having a ChatThreadClient means only having access to ChatThreadProperties whereas ChatClient.GetChatThreads returns list of ChatThreadItem(s) - these objects (ChatThreadProperties and ChatThreadItem) are very similar but e.g. LastMessageReceivedOn only exists as a property on the latter?

Could these two be merged into one and the same or at least have the same set of properties?

@github-actions github-actions bot added customer-reported Issues that are reported by GitHub users external to the Azure organization. needs-triage Workflow: This is a new issue that needs to be triaged to the appropriate team. question The issue doesn't require a change to the product in order to be resolved. Most issues start as that labels Sep 26, 2024
@jsquire jsquire added Service Attention Workflow: This issue is responsible by Azure service team. Client This issue points to a problem in the data-plane of the library. needs-team-attention Workflow: This issue needs attention from Azure service team or SDK team Communication and removed needs-triage Workflow: This is a new issue that needs to be triaged to the appropriate team. labels Sep 26, 2024
Copy link

Thanks for the feedback! We are routing this to the appropriate team for follow-up. cc @acsdevx-msft.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Client This issue points to a problem in the data-plane of the library. Communication customer-reported Issues that are reported by GitHub users external to the Azure organization. needs-team-attention Workflow: This issue needs attention from Azure service team or SDK team question The issue doesn't require a change to the product in order to be resolved. Most issues start as that Service Attention Workflow: This issue is responsible by Azure service team.
Projects
None yet
Development

No branches or pull requests

2 participants