Fixes: https://github.com/microsoft/vscode/issues/115101.
See issue for details.
- Adopts the new API
- Test results now persist across reloads (last 64 runs).
- Removed state grouping in favor of sorting option.
- Code lenses are disabled for now
* draft trusted workspace service / model
* renaming
* add request model and action
* err fix
* add request handlers with mock actions
* some quick fixes
* adding badge icon to activity bar gear
* Add Statusbar item to indicate trust
* Cleanup code
* Add background color
* Use theme color for the status background color
* adding basic editing experience
* observe trust with startup tasks
* Extension enablement
* Add capability to provide a custom message
* Remove old actions
* explorer: if you can not undo, pass undo to editor
fixes#111630
* Remove plug icon from ports view
Part of https://github.com/microsoft/vscode-internalbacklog/issues/1689
* Fixed compilation error
* Handle extension uninstall
* Handle extension install
* Ability to prompt when state is untrusted
* Do not change state is the modal dialog is dismissed or the Cancel button is pressed
* Refactored enablement code
* Prompt when installing from VSIX
* Prompt when installing from the Gallery
* Move file into the browser folder
* fixes and polish
* restructure workspace contributions
* restructure actions and use confirmations
* Initial draft of the proposed APIs
* Added stubs for the proposed api
* Trusted Workspace proposed API
* Fix a regression introduced by merge
* status bar indicator improvements
* remove helper command as we now have hooks
* verbose messaging for the immediate request
* add indication to global activity icon of pending request
* try personal title
* Add configuration setting
* Add additional extension actions
* Fix contributions
* Removed context key that is not needed
* Fixed issue with the dialog
* Reduce arbitrary event limiter from 16ms down to 4.16666 (support for monitors up-to 240hz) #107016
* Fixes#115221: update emoji tests
* Give a higher priority to language configuration set via API call (#114684)
* debug console menu action polish
* Avoid the CSS general sibling combinator ~ for perf reasons
* more notebook todos
* Use label as tooltip fallback properly
Part of #115337
* Fixesmicrosoft/monaco-editor#2329: Move `registerThemingParticipant` call to `/editor/`
* Fix port label not always getting set
Part of microsoft/vscode-remote-release#4364
* simplify map creation, fyi @bpasero
* Fix#114432: Multiple save dialogs appearing on Windows if Ctrl+S is pressed multiple times (#114450)
* fix multiple save dialogs appearing on Windows when spamming Ctrl+S
* remove old fix and instead keep track of windows with open dialogs in the dialogMainService
* keep initialisation of activeWindowDialogs in constructor
* remove unused variable
* some changes
* queue dialogs based on hash of options
* simplify structure, fix comment typo
* Apply suggestions from code review
Co-authored-by: Benjamin Pasero <benjamin.pasero@gmail.com>
* remove unnecessary async/await for aquireFileDialogLock method
* don't acquire file dialog lock for message boxes
* use MessageBoxReturnValue | SaveDialogReturnValue | OpenDialogReturnValue instead of any type for getWindowDialogQueue
* Apply suggestions from code review
Co-authored-by: Benjamin Pasero <benjamin.pasero@gmail.com>
Co-authored-by: Benjamin Pasero <benjpas@microsoft.com>
Co-authored-by: Benjamin Pasero <benjamin.pasero@gmail.com>
* 💄 dialog main service locks
* debt - adopt some ? operator
* Better hiding of custom hover in icon label
* Limit to 8ms (120fps)
* more API todos for notebooks
* 💄
* Update grammars
* chore - group notebook specific api proposals together
* added unreleased fixes to endgame notebook
* Add changes back to the modal dialog
* Add back the workspace trust proposed APIs
* Adjust dialog buttons
* Standardize on WorkspaceTrust name across interfaces, classes, variables
* Renamed some of the missing keys
* Add TestWorkspaceTrust stub and fix failing tests
* Add requiresWorkspaceTrust property to fix test failure
* remove notebook change
Co-authored-by: Ladislau Szomoru <lszomoru@microsoft.com>
Co-authored-by: isidor <inikolic@microsoft.com>
Co-authored-by: Alex Ross <alros@microsoft.com>
Co-authored-by: TacticalDan <gorksorf@gmail.com>
Co-authored-by: Alexandru Dima <alexdima@microsoft.com>
Co-authored-by: Johannes Rieken <johannes.rieken@gmail.com>
Co-authored-by: Cameron <cameron532@gmail.com>
Co-authored-by: Benjamin Pasero <benjpas@microsoft.com>
Co-authored-by: Benjamin Pasero <benjamin.pasero@gmail.com>
Fixes#114543
External and internal callers to openExternal may not expect (or want) their urls to be handled by a contributed opener. This change makes it so you have to explicitly enable using contributed openers when calling openExternal.
It also enables using contributed openers for a few places in our codebase
For #109277
- Add `option` opener priority. This means the oper will only be shown if requested but will not replace the default opener
- Persist registered openers for IntelliSense suggestions
If the user has configured a specific external uri opener, we should always try to use that without first calling `canOpen` to filter down the list of openers.
This change also adds `ExternalUriOpenerEnablement` which allows an opener to mark itself as the preferred opener for a given uri. If only a single preferred opener is returned, it will be used automatically for that uri (although user configuration can override this)
This changes makes a few changes to the openers:
- Move the opener prompting from the extension host into the main thread
- Make the external opener process two phases: get openers and then open. This would let us skip the trusted domain validation for extension handled links if we want to in the future
- Add lifecycle to commands used by the uri opener
For #109277
