* temporarily changing the funcion onFromat to be able to trigger the sorting on real examples
* adding the DocumentSortingRequest
* accesssing directly the text edits from the request
* added code in order to provide the link between the json sorting capabiliites and vscode
* adapting to the new api output of the sort function
* instead of using await use then inside of the command that registers
* textEditor replaces window.activeTextEditor
* adding changes from review
* update service
* use SortOptions
---------
Co-authored-by: Martin Aeschlimann <martinae@microsoft.com>
As stated in the docs for "editor.findMatchHighlightBackground":
"The color must not be opaque so as not to hide underlying decorations."
I've simply added a 0.6 opacity to the color so that it doesn't obscure the selection background.
* Add shellscript `filenamePatterns` for `.env*`
In some cases, projects use `.env` files such as `.env.development`
or `.env.production` or similar things.
Adding this to extensions/shellscript/package.json as a
`filenamePatterns` avoids developers having to add specific
`"files.associations"` to their VS Code settings files.
Fixes#173425
* Change pattern from .env* to .env.*
Fixes#173707
We previously converted the TS Server log from a simple string to an object. However there were a few cases where this object was incorrectly being converted into a UI string, resulting in `[Object object]`
* Unfreeze Git Commit Message grammar II
Before this change, the upstream for the VSCode Git grammar was dead.
Also, the test setup for that project has been EOL since 2014, so even
just running the tests was difficult.
The replacement grammar, unlike the current grammar:
* Has a vscode-tmgrammar-test test suite that is runnable and passing
and that will run in CI for any PRs (in the upstream project)
* Has diff highlighting for Swedish as well as English (#133888)
* Highlights touched files both in Swedish and in English
Fixes#133888Fixes#168847
Ref: <https://github.com/walles/git-commit-message-plus>
And for the record, I was the one setting up the new Git Commit Message
project. And it was fun!
* Remedy review feedback
Retain the line-too-long subject line highlighting. Improved to
highlight only the too-long part, but same idea still.
Special case English language file operations keywords and retain the
previous classification of those. But fallback to op-and-filename
classification when that fails (like it will for Swedish git for
example).
* Update colorize test result
* Update script and cgmanifest
---------
Co-authored-by: Alex Ross <alros@microsoft.com>
