[Bug Bash] Invalid package pattern can be added successfully into the “Package Source Mapping” list

[v-luzh]

NuGet Product Used

Visual Studio Package Management UI

Product Version

Dev\6.5.0.43

Worked before?

No response

Impact

It bothers me. A fix would be nice

Repro Steps & Context

Details about the problem

VS Version: Main\33026.144
NuGet Version: Dev\6.5.0.43
OS Version: Windows-11-Enterprise-21H2 ENU

Repro Steps:

1. Open VS, click menu File->New Project, create a Console App (.Net Core) project.
2. Right-Click the project in the Solution Explorer window and select ‘Manage NuGet Packages…’.
3. Click the “settings” button on the right panel and click “Package Source Mapping” tab.
4. Click “Add” button, type invalid string in the package pattern text-box and select a package source in the source list below.
5. Click “Add” button on the bottom.

Expected:

Invalid package pattern can not be added into the “Package Source Mapping” list.

Actual:

Invalid package pattern can be added successfully into the “Package Source Mapping” list as below.

Notes:

It’s not a regression since it is a new feature.

Verbose Logs

No response

[jeffkl]

Team Triage: /cc @donnie-msft

[donnie-msft]

The behavior is intentional as Validation was not spec'd for the initial release. We may eventually introduce validation here, but until we know more, this input field behaves the same as modifying the config XML manually.

[SueSu01]

It still reproes on VS Main\35222.175 + NuGet Client Dev\6.12.0.82.