* Add panelTitleBadge color variables
* Revert builtin theme changes
* Move panel section in theme.ts
* Use ACTIVITY_BAR_BADGE_* styles as default for PANEL_TITLE_BADGE_*
* Add a token store for tree sitter
* Handle root node change
* Split tokens, changes between syntax nodes, proper new end position when multiple edits
* Holes between nodes
* Add guess token store
* Fix deleting tokens
* Switch over to range based and capture offsets early
* 🧹
* 🗑️
* Only block for 5 ms, comments in monaco.d.ts
* Faster and more scoped changed range finding
* Revert "Faster and more scoped changed range finding"
This reverts commit 84b3f4a612.
* Faster and more scoped changed range finding
* Use already computed end position
* Only expose fully parsed trees from tree sitter and do capture immediately.
* Improve race by only firing tree change event when the tree parse is on the same version as the model
* Fix race
* Fix disposable leak in test
* Fix parsing loop bug
* Fix race condition in the token store layer
* Don't block when collecting tokens
* Fix tests
* Fix some tests
* Add Performance to CORE_TYPES
* Add missing js file
* Check for cyclic dependencies during compile
Changes gulp-tsb to check the emitted JS code for cyclic dependencies. Historically we never cared about cycles between TS files as long as they dissappeared after compile (e.g type-dependencies, not runtime dependencies)
https://github.com/microsoft/vscode-internalbacklog/issues/5271
* fix cycling dependencies
fyi @aeschli @aiday-mar
* remove cyclic dependency with unused `BasedTextEdit` fyi @hediet
* remove cycle between chatEditService and chatEditingSession
fyi @alexdima
* remove cyclic dependency between chatSetup and chatViewPane
fyi @roblourens
* better cycle detection
* don't check cycles when not needed
* clear graph when reprocessing file dependencies
* remove cycle between with `notebookChatEditController` fyi @DonJayamanne
* modernize and cleanup tsb/utils
* #84756 Support object type policy
* add new policy object for array and object
* add new policy object type
* checkin policies.js file
* review
* fix warning
---------
Co-authored-by: João Moreno <joao.moreno@microsoft.com>
This adopts the `NativeBrokerPlugin` provided by `@azure/msal-node-extensions` to provide the ability to use auth state from the OS, and show native auth dialogs instead of going to the browser.
This has several pieces:
* The adoption of the broker in the microsoft-authentication extension:
* Adding `NativeBrokerPlugin` to our PCAs
* Using the proposed handle API to pass the native window handle down to MSAL calls (btw, this API will change in a follow up PR)
* Adopting an AccountAccess layer to handle:
* giving the user control of which accounts VS Code uses
* an eventing layer so that auth state can be updated across multiple windows
* Getting the extension to build properly and only build what it really needs. This required several package.json/webpack hacks:
* Use a fake keytar since we don't use the feature in `@azure/msal-node-extensions` that uses keytar
* Use a fake dpapi layer since we don't use the feature in `@azure/msal-node-extensions` that uses it
* Ensure the msal runtime `.node` and `.dll` files are included in the bundle
* Get the VS Code build to allow a native node module in an extension: by having a list of native extensions that will be built in the "ci" part of the build - in other words when VS Code is building on the target platform
There are a couple of followups:
* Refactor the `handle` API to handle (heh) Auxiliary Windows https://github.com/microsoft/vscode/issues/233106
* Separate the call to `acquireTokenSilent` and `acquireTokenInteractive` and all the usage of this native node module into a separate process or maybe in Core... we'll see. Something to experiment with after we have something working. NEEDS FOLLOW UP ISSUE
Fixes https://github.com/microsoft/vscode/issues/229431
