Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Extensions filter for publisher should be exact #151192

Closed
Tracked by #154
aquarion opened this issue Feb 8, 2022 · 17 comments
Closed
Tracked by #154

Extensions filter for publisher should be exact #151192

aquarion opened this issue Feb 8, 2022 · 17 comments
Assignees
Labels
bug Issue identified by VS Code Team member as probable bug extensions Issues concerning extensions
Milestone

Comments

@aquarion
Copy link

aquarion commented Feb 8, 2022

Does this issue occur when all extensions are disabled?: Yes/No

  • VS Code Version: 1.62.3
  • OS Version: Windows 10

Steps to Reproduce:

  1. Go to an extension by a verified publisher in the extensions view, example: "GitHub Pull Requests and Issues"
  2. Click the publisher name next to the shiny tick star to see other extensions by "this" publisher.
  3. Note the inclusion of any publisher with the original publisher in the name. For example "Github Octo", "Correia GitHub Gruvbox".
  4. This could confuse an unwary user into installing an unverified extension thinking it was by a trusted publisher.

Suggestion for fixing: Publisher filter should be an exact, not partial, match.

@sandy081 sandy081 transferred this issue from microsoft/vscode Feb 8, 2022
@sandy081 sandy081 assigned prashantvc and unassigned sandy081 Feb 8, 2022
@sandy081
Copy link
Member

sandy081 commented Feb 8, 2022

CC @isidorn

@isidorn
Copy link
Contributor

isidorn commented Feb 9, 2022

I agree this is a bug, and we should fix this. For reference here's the image.

Screenshot 2022-02-09 at 11 47 20

@isidorn isidorn added the bug Issue identified by VS Code Team member as probable bug label Feb 9, 2022
@prashantvc
Copy link
Contributor

We are tracking all search related issue at microsoft/vsmarketplace#154

@prashantvc prashantvc added the search Search widget and operation issues label Feb 11, 2022
@SaiKanth007
Copy link

Similar to categories filter, marketplace also provides support for publisherName filter, which can be leveraged to search for extensions belonging to a specific publisher.

@sandy081 VSCode can map to this filter for filtering on publisherName (filterType=18)

@sandy081 sandy081 transferred this issue from microsoft/vsmarketplace Jun 3, 2022
@sandy081 sandy081 added extensions Issues concerning extensions and removed search Search widget and operation issues labels Jun 3, 2022
@sandy081 sandy081 added this to the June 2022 milestone Jun 3, 2022
@sandy081
Copy link
Member

sandy081 commented Jun 3, 2022

Thanks @SaiKanth007. I am not aware of this filter type. Moving this to VS Code repo to support it.

@microsoft microsoft deleted a comment from vscodenpa Jun 3, 2022
@isidorn
Copy link
Contributor

isidorn commented Jun 3, 2022

@SaiKanth007 thanks for letting us know. Might there be some other filters we are not using and we should? Thanks

@SaiKanth007
Copy link

@isidorn currently we don't have any public documentation of the API to list down the different filterTypes we support. So sharing you the details on the teams chat.

@sandy081
Copy link
Member

@SaiKanth007 Does this filter takes publisher id or publisher display name?

@SaiKanth007
Copy link

It accepts publisher id.

I just saw that filtering on publisher id works as expected when there is no search text. (Unlike other VSCode calls which hit AzureSearch/Marketplace cache this hits marketplace DB - could become expensive as the load for this scenario increases)

Also, it breaks when we provide search text along with publisherId filtering (which I guess is what users eventually need). I will create an issue for both of this on our side and track it.

We are working on migrating search scenarios to our new platform, and I will check if this can be fixed there. Otherwise, we will try to fix it in the existing code.

@sandy081
Copy link
Member

It accepts publisher id.

@isidorn It means this breaks when publisher name is Microsoft because not all Microsoft extensions have same publisher id.

@isidorn
Copy link
Contributor

isidorn commented Jun 10, 2022

@sandy081 that sucks. That would be worse than the current state of things.
@SaiKanth007 is there some way to do the filtering based on publisher display name due to the case Sandeep described.

@sandy081 sandy081 modified the milestones: June 2022, Backlog Jun 29, 2022
@prashantvc
Copy link
Contributor

prashantvc commented Aug 19, 2022

As user user, I expect:

  1. publisher filter should accept both lower case or upper case text (i.e case insensitive)
  2. publisher filter must return exact match for publisher display name, or publisher ID
  3. If publisher display name includes multiple words, they should be put into double quotes.

    for example, publisher:"microsoft devlabs".

@prashantvc
Copy link
Contributor

This is fixed in the latest Insiders. @aquarion Could you try it?

@usernamehw
Copy link
Contributor

Is publisher title unique? For example, clicking on the publisher title in VSCode:

Publisher id still doesn't work:

Version: 1.73.0-insider (user setup)
Commit: 266ff5b

@isidorn
Copy link
Contributor

isidorn commented Oct 20, 2022

Yes, unfortunately the display name is not unique.
@prashantvc ideally we would make this unique. Not sure if this is possible or planned?

@prashantvc
Copy link
Contributor

We do make sure that Display Name is unique for enterprises and well-known publishers. But, not for everyone, this is something we have on the backlog but not planned

@isidorn
Copy link
Contributor

isidorn commented Oct 31, 2022

Closing this as no further plans to improve here I think.

@isidorn isidorn closed this as completed Oct 31, 2022
@github-actions github-actions bot locked and limited conversation to collaborators Dec 15, 2022
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
bug Issue identified by VS Code Team member as probable bug extensions Issues concerning extensions
Projects
None yet
Development

No branches or pull requests

7 participants