Содержание

Validating schema changes

Open the schema in VsCode, and some test json file in another pane.
Add the following to the top of the file
```
 "$schema": "file:///Users/migrie.REDMOND/dev/public/terminal/doc/cascadia/profiles.schema.json",
```
But, you know, with your actual path/to/the/terminal. Use this instead of the https one that points at the one in main.
I'd recommend getting rid of your profiles and actions, just in case. I constantly have deprecated and experimental things in my settings that have never merged.
There's a button at the botton of VsCode which is VERY useful:

That'll help you reload the schema in the editor when you make changes.

Manually test different Terminal branding locally

Place this in Directory.build.props in the solution root

<?xml version="1.0" encoding="utf-8"?>
<Project DefaultTargets="Build" xmlns="http://schemas.microsoft.com/developer/msbuild/2003">

  <PropertyGroup Label="Branding">
    <!-- For testing purpose: manually change the branding of the Terminal you build -->

    <!-- <WindowsTerminalBranding>Preview</WindowsTerminalBranding> -->
    <!-- <WindowsTerminalBranding>Release</WindowsTerminalBranding> -->

    <!-- Not settings one of the above will default to "dev" -->
  </PropertyGroup>
</Project>

Test terminal PRs Locally

Click "details" under "Terminal CI (Build x64 Build x64 Release Dev) " in the CI results.
On the page that opens, click "View more details on Azure Pipelines".
Search the page for "artifacts" (note spelled with an i). You'll find a link labelled n artifacts produced where n is some number. Click that link.
This page is a bit fiddly. Find the table on the page, then switch to browse mode. Down arrow through the rows until you reach one labelled "drop", then hit right arrow.
In the menu that opens, down arrow to "download artifact" and press enter.
Extract the zip you downloaded. Inside the drop\appx folder, you'll find a CascadiaPackage_0.0.1.0_x64.msix. Rename it to a .zip and extract.
From that directory, run WindowsTerminal.exe to test wt, or OpenConsole.exe to test conhost.

This makes some assumptions that you already have the VCLibs installed and other dependencies, but for the most part it should work.