"Incomplete" color schemes are rejected as if they don't exist (possibly only if in fragment)

[Diablo-D3]

Windows Terminal version (or Windows build number)

1.11.2421.0, 1.10.2383.0

Other Software

No response

Steps to reproduce

Use a color scheme that is "incomplete" in a fragment, use the scheme name's in your default profile.

Example:

{
  "schemes": [
    {
      "name": "Test",
      "background": "#000000",
      "foreground": "#000000",
      "black": "#002b36",
      "red": "#6a4d53",
      "green": "#468666",
      "yellow": "#75896c",
      "blue": "#002b36",
      "magenta": "#6a4d53",
      "cyan": "#468666",
      "white": "#75896c",
      "brightBlack": "#002b36",
      "brightRed": "#002b36",
      "brightGreen": "#002b36",
      "brightYellow": "#002b36",
      "brightBlue": "#002b36",
      "brightMagenta": "#002b36",
      "brightCyan": "#002b36",
      "brightWhite": "#002b36"
    }
  ]
}

Drop in %LOCALAPPDATA\Microsoft\Windows Terminal\Fragments\Test\Test.json, and change settings.json's defaults: colorScheme to Test. Launch WT, get greatly misleading warning.

Notice the use of #11456 here. Else, everything seems to be listed as per the documentation on schemes.

Change "Magenta" to "Purple" on both lines, and watch the fragment suddenly be discoverable and work.

Also note: the colors in this scheme are garbage on purpose, if they're ugly, its working.

Expected Behavior

Either working behavior (with the missing colors replaced with Campbell's) and/or a warning specifically telling me what is wrong with the scheme. At no point should WT tell the user that the scheme doesn't exist without any other warnings that specifically state the scheme was found, but is incomplete.

Actual Behavior

On launch with incomplete scheme in fragment, but specified in settings.json

Notice the lack of saying the color scheme exists, but misses elements; it just claims it never existed ever, which leads to a day long wild goose chase.

[SufyaanKhateeb]

If no one is assigned, maybe I look into this.

[zadjii-msft]

@SufyaanKhateeb Go right ahead ☺️

[SufyaanKhateeb]

While building the application I am running into

  D:\Windows Kits\10\Include\10.0.22621.0\shared\TraceLoggingActivity.h(439,1): fatal  error C1060: compiler is out of heap space (compiling source file Ne
wTabMenuTests.cpp) [C:\Users\sufya\OneDrive\Desktop\Sufyaan\windows-terminal\src\cascadia\LocalTests_SettingsModel\SettingsModel.LocalTests.vcxproj]
  D:\Windows Kits\10\Include\10.0.22621.0\shared\TraceLoggingActivity.h(847,1): fatal  error C1060: compiler is out of heap space (compiling source file Se
rializationTests.cpp) [C:\Users\sufya\OneDrive\Desktop\Sufyaan\windows-terminal\src\cascadia\LocalTests_SettingsModel\SettingsModel.LocalTests.vcxproj]

How much memory space does this require for building?

[zadjii-msft]

Like, at least 4GB. The precompiled header files for XAML are outrageously big, and they need to be entirely stuffed into memory all at once.

[MaximilianMeiler]

First-time contributor here - I'm interested in working on this issue. I'll try to get the environment set up - perhaps the error should be expanded to include what sections of which schemes are missing?

[SufyaanKhateeb]

Yes, you can go ahead. I didn't get time to check it out.

[MaximilianMeiler]

I've set up my development environment (including an installation of the Windows 10.0.22621.0 SDK), but am still getting this error on launch. I'm not able to find the "retarget solution" option for the OpenConsole file and have tried a few workarounds, to no success - any aid would be appreciated.

[MaximilianMeiler]

I was able to solve the above issue by un/reinstalling my SDKs and performing a repair on Visual Studio. However, i'm now getting a different error when attempting to build with powershell:

Attempting to build with the command prompt gives the powershell version error as well.

As before, any assistance is appreciated.

Edit: Now I'm getting the "error NETSDK1004: Assets file not found. Run a NuGet package restore to generate this file." error instead.