Cli-microsoft365: New command: teams deeplink tab generate

[garrytrinder]

Usage

teams tab deeplink get [options]

Description

Generates a Microsoft Teams deep link from an existing Tab in a Channel

Options

| Option | Description |
| ----------------------- | ----------------------------------------- |
| --teamId <teamId> | The ID of the team where the tab exists |
| --channelId <channelId> | The ID of the channel where the tab exists |
| --tabId <tabId> | The ID of the tab to generate the deep link from |
| --label <label> | The label to use in the deep link |
| --tabType <tabTypeOptions> | The tab type. Allowed values Static,Configurable |

Additional Information

Generating a deep link to your tab - https://docs.microsoft.com/en-us/microsoftteams/platform/concepts/build-and-test/deep-links#generating-a-deep-link-to-your-tab

Format of the deep link for a configurable tab should be

https://teams.microsoft.com/l/entity/{appId}/{entityId}?webUrl={contentUrl}&label={label}&context={context}

Format for a static tab should be (omitting context)

https://teams.microsoft.com/l/entity/{appId}/{entityId}?webUrl={contentUrl}&label={label}

{appId}, {entityId} and {contentUrl} can be obtained from the Tab object returned by Microsoft graph.

[nanddeepn]

Hi @garrytrinder
I am interested to work on this.

[garrytrinder]

Great, it's all yours 👍🏻

Thank you for the help 👏🏻

[nanddeepn]

Hi @garrytrinder
I have raised PR. Please review and guide on code coverage part. Couple of code lines are reported as uncovered.
Thank you.

[nanddeepn]

Hi @garrytrinder, @waldekmastykarz
Code coverage is fixed. Please review.

[waldekmastykarz]

Tad late to the party, but is there a reason to use generate as the verb rather than the more common get that we're using in other commands?

[garrytrinder]

That's a fair point @waldekmastykarz no reason why I can't be get.

[waldekmastykarz]

Thinking of it more, was there any particular line of thought to have it named teams deeplink tab rather than teams tab deeplink? Tab is a known artifact in teams, similar to channels and messages. Deeplink on the other hand is a property of a tab so from the hierarchy point of view it should go after tab. Thoughts?

[garrytrinder]

Another fair point @waldekmastykarz and your comments do make a lot of sense, I've updated the spec to take on board your comments.

[garrytrinder]

Closing issue as per discussion on associated PR.