Closed Jwaegebaert closed 8 months ago
@pnp/cli-for-microsoft-365-maintainers any thoughts?
Can't we include almost every command group? Like: planner, OneDrive, Outlook, Purview, ...
Yeah, I was thinking something similar. We could something like this:
"keywords": [
"adaptive card",
"ai builder",
"azure active directory",
"azure ad",
"azure",
"bookings",
"dataverse",
"entra id",
"graph",
"m365",
"microsoft 365",
"microsoft",
"o365",
"office 365",
"onedrive",
"onenote",
"outlook",
"planner",
"power apps",
"power automate",
"power platform",
"purview",
"search",
"sharepoint framework",
"sharepoint online",
"sharepoint",
"skype",
"spfx",
"teams",
"tenant",
"todo",
"viva connections",
"viva engage",
"viva",
"yammer"
],
A few more to consider
AI Builder Dataverse Viva Engage Viva Connections Bookings Entra ID
Good idea. Let's build a complete list that we can use across all our packages.
I've updated the list here: https://github.com/pnp/cli-microsoft365/issues/5433#issuecomment-1699077655
@pnp/cli-for-microsoft-365-maintainers any more ideas?
Looks good to me, my only remark is that it's actually called microsoft entra id
.
Most apps have microsoft
in their name, but that would slightly clutter the keywords.
It's been some time since we last reviewed the keywords we've set in the
package
file. We observed this in theaction-cli-deploy
repo (https://github.com/pnp/action-cli-deploy/pull/26#discussion_r1302979041), and it might be valuable to include a couple of extra keywords. Whatever decision we make here, let's ensure that these modifications are applied across all other M365 CLI repositories.At present, within the
action-cli-deploy
repo, some adjustments have already been made, resulting in the following: