-
Notifications
You must be signed in to change notification settings - Fork 16
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. Weβll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Refactor action naming #294
base: dev
Are you sure you want to change the base?
Conversation
β¦pnp#246 (pnp#280) ## π― Aim The aim is to refactor the way start and run commands in integrated VS Code terminal. The idea is to aling the approach by using the dedicated Terminal service which was developed for exactly that. ## β What was done - [X] Removes all direct usage of `terminal` and refactors it to same approach ## π Related issue Closes: pnp#246
β¦sions. Closes: pnp#200 (pnp#281) ## π― Aim This PR implements the required settings of issue [pnp#200](pnp#200). ## π· Result ![image](https://github.com/user-attachments/assets/ec83766a-d8c6-45f9-ad49-29fb53b82703) ## β What was done Added two settings for the extension: - showServiceIncidentList - showTenantWideExtensions Updated the `TerminalCommandExecuter` extracting the `getExtensionSettings` method and creating a dedicated util file. Updated the `CommandPanel` to keep into account the new settings when loading and showing data. ## π Related issue Closes: pnp#200 --------- Co-authored-by: Saurabh Tripathi <[email protected]> Co-authored-by: Adam WΓ³jcik <[email protected]> Co-authored-by: Luccas Castro <[email protected]> Co-authored-by: Adam WΓ³jcik <[email protected]>
## π― Aim The aim is to make account and enviroment views more bulletproof and properly display views when CLI command extecution gets rejected due to lack of permission ## π· Result ![image](https://github.com/user-attachments/assets/4b49a22d-a33f-4785-ab31-e6b73afe21e9) ## β What was done - [X] Added simple error handling to cover the reject case ## π Related issue Closes: pnp#278
## π― Aim Adding an extra filter to Sample gallery so that we can filter on the extension type. Filter can only be visible when extension type is selected 'Component Type' ## π· Result ![image](https://github.com/pnp/vscode-viva/assets/35696168/c8c2e084-5831-4fc4-861e-ad4c4c0845d7) ## β What was done - [X] Added Extension filter dropdown - [X] Added functionality so that extension filter is only visible when extension is selected in the Component Type dropdown - [X] Added filter functionality so that samples get filtered based on selected value in extension dropdown - [x] Added filter functionality so that samples don't get filtered when extensions dropdown has selected values but extension is not selected in component type dropdown ## π Related issue Closes: pnp#219
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Unfortunately, this is only part of what needs to be done for this issue. As part of this change we should also align the commands naming (those are present in VS Code when using the F1 and searching for commands for SharePoint Framework Toolkit). We should also align the commands naming to be the same as we see in the actions tree.
Those may be found in the package.json
file
https://github.com/pnp/vscode-viva/blob/d241081aa95aea583aa94354c8d0ade82c91ec6b/package.json#L297C4-L310C47
@maximkol awesome start. I left a small comment as I think this PR is missing part of implementation that is described in the related issue. Please do give it a recheck π |
d3fe8fc
to
5359569
Compare
@maximkol we just had a new major v4 release. Due to this the |
@maximkol any updates on this PR? |
π― Aim
To update actions naming
π· Result
β What was done
π Related issue
Closes: #287