* Sort chat history entries by lastMessageDate
* Add date labels to chat history picker
* Remove unused dynamic 'isDefault'
* Add ChatTitleProvider
* Disallow deleting and moving active chats
* Add test for new data normalization
* Fix build and add test
* Fix new test
* Moves the `setupRefresh` stuff into the CachedPublicClientApp simplifying things a bit
* Uses a ScopeData class to handle all scope operations fixing an issue where we were passing in the wrong array into the `acquireTokenInteractive`
* new API option and flag
* show the notebook as a repl
* handle any notebook type, dispose all model refs
* open notebook doc as scratchpad
* delay loading the model for untitled notebooks until shown
* add initial content consistently for untitled
* simplify utitled notebook creation
* recover open untitled notebook as dirty behavior
So that all auth providers can take advantage of this logic. This basically will do a light enforcement that the account you signed in to matches the account that was requested (if it was specified).
This is needed for finalization.
Try to fix ata perf issues on web
For #182791
With this change, we now make a single call to the package manager per root instead of per package. This simplifies the code and should be better for perf
Still seeing a bunch of errors in the console but TS typing is working ok. Needs more exploration for ATA
* Fix some always true/false errors in codebase
Testing out latest TS nightly that can identify when an expression is always true/false. This caught a few likely coding mistakes in our codebase
Unsure about the intent in some of these cases but I've tried my best to understand them. Pinging relevant code owners for the confusing cases
* Bump TS version
* Fix unreachable in build scripts
* Bump versions
* restore intent
* Revert package.json change
* Fixing a few new layer checker errors
These are global in node now
* Skip lib check in integration project
* One more skiplibcheck
* More skip lib
---------
Co-authored-by: Benjamin Pasero <benjamin.pasero@gmail.com>
Fix#221299
toResource throws here because we're tyring to watch directories outside of the workspace root. Should be fixed on TS side. Until them, adding a `catch`
It seems like this event fires in Codespaces... my _guess_ is that Codespaces basically overwrites all the settings from settings sync which causes this event to fire.
It's surprising to me that this event fires even though the value hasn't changed.
I can't repro this with the test resolver, and I also cant have Codespaces use Code - OSS, so we'll just have to see how this goes.
This _should_ do the trick though.
Fixes https://github.com/microsoft/vscode/issues/223508