microsoft / microsoft/winget-cli-restsource

Support Normalized PackageName And Publisher package match field search

Open
#59 2 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Issue-Feature
Dominant language
C#
Stars
317
Forks
79
PR merge metrics
No merged PRs in 30d

Description

Brief description of your issue

The current reference implementation does not support Normalized package name and publisher search, which is used for correlating packages with ARP entries. The support for this should be added for better correlation of packages.

The Rest schema only supports search for a single KeyWord in Request Match, but NormalizedPackagenameAndPublisher field requires two keywords, one for PackageName and another one for Publisher.
Another alternative would be to deprecate NormalizedPackagenameAndPublisher in favor of two fields NormalizedPackageName and NormalizedPublisher. A new match type can also be added to support normalized search as well instead of these.

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by tracing the REST schema's Request Match handling and the reference implementation's search path for NormalizedPackagenameAndPublisher. Resolve whether the schema should accept two keywords, split the field, or add a normalized match type. Done means the chosen design supports normalized package-name and publisher matching for ARP correlation, with its behavior verified in the relevant search coverage.

Written by the indexing model from the issue text.

Assessment

Tech stack
csharp
Domain
api, backend-api-design
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.