JSON locale Schema does not match REST Source

[Trenly]

Brief description of your issue

The JSON Schema shows that Moniker is valid in the locale manifest file and the defaultLocale manifest file. The REST source shows that locale does not contain Moniker and that defaultLocale extends locale adding only the moniker field

Steps to reproduce

Compare the 1.0.0 JSON Schema to the 1.0.0 REST Source
Compare the 1.1.0 JSON Schema to the 1.1.0 REST Source

Alternative Reproduction steps

1. Clone the winget-pkgs repository and open it in VS Code
2. Find a package that has a locale and a defaultLocale (I used Google chrome)
3. Edit the locale manifest to have a moniker key and save the file
4. Run winget validate <path-to-manifest> on the manifest you just edited
5. Note that it shows a warning that Moniker is unknown

Expected behavior

The JSON schema should match the behavior exhibited by WinGet and the REST source

Actual behavior

These items do not match

Environment

PS C:\WINDOWS\system32> winget --info
Windows Package Manager v1.1.12653
Copyright (c) Microsoft Corporation. All rights reserved.

Windows: Windows.Desktop v10.0.19043.1237
Package: Microsoft.DesktopAppInstaller v1.16.12653.0

[denelon]

Is this the same as #1592?

[Trenly]

Is this the same as #1592?

No, this is not. This is a separate issue where the field "Moniker" exists in the JSON schemas manifest.locale.1.0.0.json and manifest.locale.1.1.0.json when it shouldn't.

#1592 appeared to me to be talking specifically about how the "Locale" field for an installer entry and "PackageLocale" field should have the same validation but don't

[denelon]

Thanks, I was multi-tasking too many things at the same time.