Hi Adam

I've noticed that there is a typo on the README.md page.

The current solution (extension) is in prototype faze so may not have regular releases.

I do believe that 'faze' should be replaced with phase 😃.

Great extension!

🎯Aim

the aim of this issue is to add IntelliSense for CLI for M365 commands so that VS code will suggest options (also optional) related to that command and if an option is a select type it should suggest correct values

Discussed in #1

📝 Describe the bug

in sample gallery it is only possible to input small letters

👣 Steps To Reproduce

Steps to reproduce the behavior:

1. Go to sample gallery
2. try ti input something with caps

📜 Expected behavior

should be possible to add large letters

🎯 Aim of the feature

add search and copy code button

🎯 Aim

make the search window in the command list fixed so it is always visible when scrolling the list

🎯 Aim

when creating a new script file from sample gallery it takes the first code block not the code with CLI. The aim would be to fix it

🎯 Aim

The aim is to update the ps1 script that analysis CLI repo to create snippets and data json to base on objects not on string concats 🤦

🎯 Aim of the feature

is to add a button which will redirect to repo home page in the activity bar view

📷 Images (if possible) with expected result

🤔 Additional remarks or comments

🙅‍♂️

🎯Aim

Currently I am using old versions of react-markdown and node-fetch. I should update 💪

🎯Aim
I aim to add some automatic publish to vs code marketplace on pushing to main branch with a specified tag

🔗Reference idea
Originally posted by @Adam-it in #4

📝 Describe the bug

Does not remember the state of the menu set

🎯 Aim

The aim is to improve product readme and tags

Discussed in #12

🎯Aim

Add new section to existing side bar view that will show list of script samples. The samples should be coming from CLI repo as well as script sample repo (but only CLI samples). The list should be consistent with the command docs list.
The list should allow to quickly review/check the sample in main view with a the possibility to create new local file with the sample as starting point

Discussed in #20

🪲 What is wrong?

it seems that after adding react and typescirpt support the package has to much files and packaging brings this issue

This extension consists of 3336 files, out of which 2384 are JavaScript files. For performance reasons, you should bundle your extension: https://aka.ms/vscode-bundle-extension . You should also exclude unnecessary files by adding them to your .vscodeignore: https://aka.ms/vscode-vscodeignore

this is rather not critical as it works but I think I should resolve it for future reasons

🎯 Aim of the feature

Is to add more links to CLI for M365 like directly to repo, repo wiki, discord

🤔 Additional remarks or comments

idea is to add it to the top of the command list as an additional command list action

🎯 Aim

each do md file has this added in order to render in this place the default options which may be used in any command. I would be really cool if instead of showing this we would add it's content

Discussed in #11

🎯Aim

The aim is to create some product log. Now it was one done in paint and the one used in side bar is one of vscode defaults 😋

🎯Aim

Add more rules to eslint to validate and standardize

🎯 Aim of the feature

The aim is to present CLI samples from CLI repo now that we also have sample.json in this repo

🤔 Additional remarks or comments

The sample.json from CLI repo don't store some tags like commands etc. so probably those search functionalities will not work for samples coming from CLI repo.
This could be an additional improvement to be done in CLI repo

🎯 Aim

The aim is to use the same icon for the extension and the official one used for CLI

🎯Aim

When working on #10 I thought of additional improvements to this feature. This is the list:

• Add search to command list and maybe some better styling (interesting) along the way
• Maybe reuse PnP CLI icon 🤔 (I should probably talk with Waldek if it's ok)
• Add some kind of loader and not found/not working view to the main view presenting docs

🎯Aim

I was like thinking on adding a command which would allow the user to search for a CLI command and open docs directly from it. No need to open the commands side bar to do the search

🎯 Aim of the feature

The aim of this issue is to add all authors of the sample

📷 Images (if possible) with expected result

like

ToDo

• extend script to save authors information
• show authors in card view

🎯 Aim of the feature

Currently snippets only support command line kind of languages (bash, posh) or js. But it is also possible to use CLI as API in python app. The aim would be to add snippets support for python.

🤔 Additional remarks or comments

Added based on feedback from Twitter. Seems like Twitter marketing brings some result 😅

Discussed in #9

📝 Describe the bug

Error occurs when selecting a script in CLI for Microsoft 365 VS Code Extension samples: 'Error while creating script file based on sample.

👣 Steps To Reproduce

Steps to reproduce the behavior:

1. Open the CLI for Microsoft 365 extension in Visual Studio Code.
2. Select the "CLI for Microsoft 365 Samples" option.
3. Click on the "Script" button on a sample tile.

📜 Expected behavior

A new tab should open in Visual Studio Code, and the corresponding script should load within that tab.

📷 Screenshots

💻 Desktop (please complete the following information):

• OS: Windows 11 Enterprise

🎯Aim

the aim of this issue is to add a side panel which will show a view with all CLI commands and docs.

🤔 Things to consider

the view theme should be consistent with the vs code theme

Discussed in #2

🎯 Aim

the commands list could be tree view which groups commands from the same namespace

🎯 Aim

The aim is to add a button in docs page to open the correlated CLI docs webpage

📝 Describe the bug

in tree view the commands do not show properly

📜 Expected behavior

should show as command with dots

📷 Screenshots