* make status menu configurable
https://github.com/microsoft/vscode/issues/206940
* pull inline chat zone widget into its own file
* 💄
* remove expand/crop feature
* make chat message contents scrollable
* Tear down the Authentication monolith
Major changes:
* Turn the usage functions into a proper service `AuthenticationUsageService`
* Pull out the access data stuff into its own service `AuthenticationAccessService`
* Pull out things that make sense as actions `ManageTrustedExtensionsForAccount` `SignOutOfAccount`
* Pull out random registry stuff into a proper authentication contribution
* Pull out everything else that is extension specific into its own class (and eventually it should be in MainThreadAuthentication)
* Have the new `AuthenticationService` return a provider instead of having specific methods for getting the `label` or `supportsMultipleAccounts`
* fix tests
* fix tests
* chore: update electron@28.1.4
* ci: use latest Node.js v18 release
18.18.2 has npm version that has removed the node-gyp script
which will cause native modules fail to build that rely on
something like `install: node-gyp rebuild`
Refs c93edb55f5
* chore: update rpm dependencies
* chore: bump electron@28.2.1
* chore: bump nodejs@18.18.2
* chore: bump electron@28.2.2
* chore: bump distro
* fix: revert glibc requirements for tunnel cli
* chore: address feedback on wording
* fix: only store state when user allows the prompt
* chore: update checksums for sysroot
* fix: store connection choice per distro
* update rpm deps-list
---------
Co-authored-by: Connor Peet <connor@peet.io>
* Delete CommandFollowups and make inline chat use its own types for command followups
* Add command button, render it properly
* Manage the lifecycle of commands from chat command buttons
* Handle stale session command in type converter
* Fix
* eng: allow css nesting via postcss plugin
CSS nesting has landed in most browsers at this point, but we don't want
to break users who are still stuck on old browser (mainly older iOS
devices.) This PR adds a postcss plugin to the build process that
de-nests nested CSS.
The plugin required a newer version of postcss as well, so I have
updated that and a couple other modules to their latest versions.
* update build's package.json versions too
* no absolute positioning, scrolltop compute based on sticky lines.
* remove z-index var
* compute re-write, remove init, reduce pop-in
* dispose delayer
* remove debounce
* edge case for cell 0 header, next animation frame instead of debounce
* add delayer back, further improve pop in
* remove unused param, update testing snapshots
* fix: add linux library dependency check for remote server
* chore: add faq link
* chore: move to separate file for reuse
* chore: add option to skip check
* fix: check
* fix: package path
* fix: don't forget to exit main script
* testing: finish up coverage decorations
- Adds an inline decorator for empty-range branches
- Adds hover information for inline coverage hovers
- Fixes the editor not handling decorations that get after/before
content in `updateDecorationOptions`
- Adds an option `label` for branches
- A bunch of other misc tweaks to get coverage looking nice
- Keep decorations in sync if a user makes changes in editor
* update tests
This is the first pass at decorations in-editor. This PR doesn't
actually register the contribution, as it's not ready for selfhosting
yet. This PR creates decorations that look like this. The idea is that
coverage decorations in the glyph margin will always be visibile when
there's coverage, and users can get coverage in their code via hover or
shortcut, with the intention of making coverage unobtrusive and easy to
run all the time.
The notable thing is that there is now a third glyph margin row. I
reworked some of the editor code to handle this.
Some open questions:
- The glyph margin coverage wants doesn't need to be full-width, should
we add a new 'leftmost' glyph lane instead that's thinner?
- Adding breakpoints in files with coverage is a little annoying since
the breakpoint hint widget can expand the glyph margin on lines with
coverage, and jump back over otherwise. Probably we should never
decrease the number of lanes shown whenever the cursor is over the
glyph margin.
This continues on the coverage API I started a few years ago. It adds
initial integration where a "Show Test Coverage" tree item is shown in
the Test Results view, which then opens a dedicated Test Coverage view.
The Test Coverage view is a fairly basic tree view following the draft
design, with further improvements to come.
The 'bars' widget is also built in a reusable way such that it can be
integrated into the explorer, as this was a popular ask both inside and
outside the team.
For #123713.
