- Used the suggested yml format to write our grammar given it will definitely grow in complexity. See [VSCode's guidance](https://code.visualstudio.com/api/language-extensions/syntax-highlight-guide#using-yaml-to-write-a-grammar) for more info. One thing to note, the utility to go from YAML to JSON was already a dependency of our extension.
- Added a compile TextMate task to VSCode to enable easy Run Extension -> Edit grammar -> Re-compile text mate -> reload Experiemental instance dev flows.
- Replaced the existing Razor grammar (yes this means we will lack coloring for a period of time) to ensure we can catch bugs with the in-progress grammar quicker.
- Updated the VSCode's yml settings to have the proper tab size.
- Added a simple grammar to start (escaped Razor transitions).
- Eventually this grammar will need to live in its own repo but until we get it into a reasonable state we're going to group the grammar along side the extension to ease development.
aspnet/AspNetCore#14287
- For simplicity put the unit tests in the test folder to align with all other types of test projects.
- Converted unit tests to use `yarn` and `jest`.
- Added a `Run Unit Tests` launch configuration so we can F5 in VSCode to easily debug Razor VSCode unit tests.
- Hooked new npmproj test projects into the build.
aspnet/AspNetCore#13494
- This changeset adds the following:
- src/Razor/src/Microsoft.AspNetCore.Razor.VSCode - Razor VSCode extension library
- src/Razor/src/Microsoft.AspNetCore.Razor.VSCode.Extension - Razor VSCode extension bootstrapper
- Added a `README.md` into the `Microsoft.AspNetCore.Razor.VSCode.Extension` to describe its purpose.
- Moved old Razor VSCode project bits from `npm` to `yarn`
- Added a global .vscode folder to allow having VSCode open at AspNetCore-Tooling root yet still be able to ctrl + f5 the extension
- Expanded the bootstrapper extension project (`Microsoft.AspNetCore.Razor.VSCode.Extension`) to have new commands to make working with projects in experiemental instances easy. Prior to this we relied on a node.js script that were unsupported to magically wire things together. As part of the merging of this repo I had to find an alternate route to do that.
- Added a Razor global tslint file which each VSCode project inherits from
- Added a Razor global tsconfig file which each VSCode project inherits from
- Updated npmproj's to ensure build incrementalism works.
aspnet/AspNetCore#13494
Tanay Parikh
Ryan Brandenburg
N. Taylor Mullen