search

pnp / vscode-viva

With the SharePoint Framework Toolkit extension, you can create and manage your SharePoint Framework solutions on your tenant. All actions you need to perform during the development flow are at your fingertips.
https://marketplace.visualstudio.com/items?itemName=m365pnp.viva-connections-toolkit
MIT License
34 stars 14 forks source link

💡 [Feature]: Add SPFx Toolkit Chat Participant #239

Closed Adam-it closed 2 weeks ago

Adam-it commented 1 month ago

🎯 Aim of the feature

The aim of this feature is to leverage the latest features added to GH copilot announced in MS Build which is extensions and release it as beta for testing

📷 Images (if possible) with expected result

No response

🤔 Additional remarks or comments

docs: https://code.visualstudio.com/api/extension-guides/chat https://code.visualstudio.com/api/extension-guides/language-model

Adam-it commented 1 month ago

known issues: the response sometimes contains code in HTML block <div class="code"....

Adam-it commented 4 weeks ago

known issues: the response sometimes contains code in HTML block <div class="code"....

seems like this is fixed and was corrected in GH Copilot chat

Adam-it commented 4 weeks ago

We should check if dev is in context of project and if it is logged in before showing some actions that require either project context or tenant info

Adam-it commented 4 weeks ago

we should check if the extension uses the currently opened file as context.

Adam-it commented 4 weeks ago

we should instruct the /setup prompt to always end with reference to docs

Adam-it commented 2 weeks ago

1.90 version was released to VS Code so we should release this as well we need to align it with latest approach which a bit changed in the official npm package we may use prompt-tsx package to save prompts in .tsx files rather than concat strings

Adam-it commented 2 weeks ago

we may adda new area /manage wich will allow to run CLI commands under the hood to retrieve info about apps

Adam-it commented 2 weeks ago

we should be more defensive in the implementation. we should check for user intent and if the prompt is not connected to coding we should handle it we should expect that the model might not exist and it is not persistent and might change in future