* Fix variables in chatAgents2 API requests
* Enable file references and the 'used references' section by default in Insiders
* Add integration tests for chat
* Fix equality
* fix test
- Implements the proposal in #190277 by adding a `contextValue` to
TestMessages added to test runs.
- Make the `FloatingClickMenu` reusable outside the editor, and uses
it to implement a `testing/message/content` contribution point.
With this extensions can do things like:
Also sends the tests as a bulk to the renderer, and implements a
prefix tree for doing invalidation checks (which I plan to adopt
elsewhere later on, perhaps in debt week.)
* Expose the focused element and event in the TreeView API
* Exposed active TreeItem through extension proposal
* Add proposal to test extension
* Merge change selection and focus events
* Finish selection+focus change in treeview
* Clean up
* Clean up
* Add checkProposedApiEnabled back in
---------
Co-authored-by: Ehab Younes <ehab.younes@sigasi.com>
Co-authored-by: Alex Ross <alros@microsoft.com>
* wip
* Allow extensions to provide a readonly message
Part of #166971
* Address feedback
* Further address feedback
* Fix some nits
* Add test
* Improve tests and respond to feedback
* Don't render editor.readOnlyMessage in the settings UI
* No need to validate the IMarkdownString
---------
Co-authored-by: Benjamin Pasero <benjamin.pasero@microsoft.com>
Co-authored-by: Alex Dima <alexdima@microsoft.com>
This fixes the range extensions get when copying an empty selection. As part of this, I've also:
- Added tests for this change
- Made the paste parts of the api optional. This is useful when a test provider only wants to add data on copy
* add `SnippetController#apply(ISnippetEdit[])`
This replaces the initial ugly trick with a more sound implementation of arbitrary snippet edits. A snippet edit can cover disconnected regions, each will be applied as separate text edit but everything will become a single `OneSnippet` instance
* add integration test for SnippetString-text edit inside workspace edit
* Remove the notebookEditorDecorationType API proposal
Fixes#146838
* Remove all the infastructure around the now removed notebookEditorDecorationType api
* Finalize NotebookEditor api proposal
Fixes#149271
This finalizes most parts of the NotebookEditor api proposal. I haven't removed the proposal entirely as there are still a few parts being left behind:
- The deprecated properties/functions
- A few contribution points such as `notebook/cell/executePrimary`
* remove extra quote
* Remove the textDocumentNotebook API proposal
All consumers have now been migrated off of this proposal, so it is safe to remove from our code
* Remove deprecated api usage from test
