New command: List the chat conversations from a Microsoft Teams chat

[arjunumenon]

Usage

m365 teams chat message list [options]

Description

List the conversations from a particular chat (1 on 1 chat OR Group chat OR Meeting Chats etc) in Microsoft Teams

Options

Option	Description
-i, --chatId<chatId>	The chat ID / Conversation ID of the Microsoft Teams Chat.

Additional Info

We hay have to use the Graph API end point - v1.0/chats/ConversationID/messages as per this documentation.

New API Permission for PnP Management Shell AAD App

For us to use the API, the AAD App needs to have the permission Chat.Read, Chat.ReadWrite. Currently the AAD App which is being used by CLI for Microsoft 365 (PnP Management Shell) does not have the permission setup. Once the PR is completed, the permission will have to applied to the AAD App.

[arjunumenon]

Hello @pnp/cli-for-microsoft-365-maintainers - Can you have a look into the specs and let me know if any modification is needed for the same.

I would also request your opinion on the placement of the new Command. Currently we have our Menu items for Teams as Microsoft Teams (teams).

So the commands which we have under that section covers about Teams team. If you are all ok with this command, I am assuming we will keep this command also underneath that renaming the section to Microsoft Teams. Do you think it make sense. Appreciate your suggestion on that as well so that I will update the spec accordingly.

[waldekmastykarz]

Thanks for the spec @arjunumenon, here's some feedback.

The v1.0/chats/ConversationID/messages API would be suitable for a teams chat message list command rather than a get as it returns all messages in the specified conversation. Let's double check the API that we want to use or adjust the command name.

So the commands which we have under that section covers about Teams team. If you are all ok with this command, I am assuming we will keep this command also underneath that renaming the section to Microsoft Teams.

This command is indeed related to Microsoft Teams so it would land under the teams group. Why do you think we should rename the section in the docs?

[arjunumenon]

The v1.0/chats/ConversationID/messages API would be suitable for a teams chat message list command rather than a get as it returns all messages in the specified conversation. Let's double check the API that we want to use or adjust the command name.

Totally with you on that point. Thanks for pointing that out 👍.
My intention of the command was indeed to list the chat messages of the chat rather than getting particular chat. I had not realized get chat do have a different meaning in the context. I will update command spec to be,
m365 teams chat message list [options]

This command is indeed related to Microsoft Teams so it would land under the teams group. Why do you think we should rename the section in the docs?

Here is my thought - currently the commands which are there in the Microsoft Teams (teams) group , majority of the command are related to Microsoft Teams team.
However, there are some commands which are coming outside the scope of Microsoft Teams team. Some of the commands are below.

1. m365 teams app publish
2. m365 teams app remove
3. m365 teams report deviceusagedistributionusercounts [options]
4. m365 teams user app add

This command which we have spec'd is also not related to Microsoft Teams team, while it is related to chat outside Microsoft Teams team. Hence I was wondering whether it make sense to rename the section in the Navigation since the commands coming under that list of commands which are both related to Microsoft Teams team as well related to commands outside Microsoft Teams team.

Pardon me if it does not make sense to the original idea / thought process

[waldekmastykarz]

So the idea behind our naming convention is that the first segment of the command name indicates a workload. In this case it's Microsoft Teams as whole, not just a specific Teams team. As such, both commands that operate on teams, channels and conversations as teams that relate to the broader Teams workload fall under the teams namespace. Does that make sense?

[arjunumenon]

As such, both commands that operate on teams, channels and conversations as teams that relate to the broader Teams workload fall under the teams namespace. Does that make sense?

Yes it does. I perceived the naming convention in a different way, that the commands are related to Teams team alone.
Your explanation make sense. All good for now 👍.

[martinlingstuyl]

Hi guys,
I'll see if I can pick this up the coming days. It would be my first contribution, so I'll need time to look into the setup.