-
-
Notifications
You must be signed in to change notification settings - Fork 460
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
[FEATURE REQUEST] Identify MSStore packages on the install section #502
Comments
Oh, you mean like treating them as winget packages (showing info, etc.)? |
That would be nice, but I was only thinking about them having a different icon from Local PC and regular Winget so I could easily differentiate the source |
I think 2d61f53 made MSStore packages appear as Winget ones, but I don't think WingetUI is able to display any info about them (because it's not available through Winget). Then maybe it doesn't make sense to have show info for these packages Icon suggestion to differentiate MSStore from Winget source: |
I appreciate your attempt, but it's not working properly. |
Regarding the ellipsis, this is the same issue as always. Microsoft messing up, and much can't be done about it. |
The problem isn't the ellipsis itself, but because of it 16 out of 19 MSStore packages are wrongly identified as Winget pkgs. Only 3 are correctly identified as being from MSStore. Is there a way to ignore the ellipsis only during the source check? |
I mean, i could omit it, but the 13-character id wouldn't be 13 characters long. |
However, i could actually fix that |
It should be now working |
Thanks! |
I know Winget-CLI ability to identify source as MSStore is broken, however I believe there's a relatively simple way this can be achieved by WingetUI. This is because MSStore packages end with an underscore and exactly 13 characters after it. For example:
JAMSoftware.TreeSizeFreePrivate_37s2tpab2h9zg
8bitSolutionsLLC.bitwardendesktop_h4e712dmw3xyy
The text was updated successfully, but these errors were encountered: