WD-17150 - aliases section in snap details#5356
Merged
alvaromateo merged 10 commits intomainfrom Nov 12, 2025
Merged
Conversation
codeEmpress1
approved these changes
Sep 8, 2025
bc2aae6 to
edc0568
Compare
46f3eec to
97cd46a
Compare
d6d52b1 to
a0a8b17
Compare
This reverts commit d965af0.
baea7cf to
8e34950
Compare
M7mdisk
added a commit
that referenced
this pull request
Nov 17, 2025
alvaromateo
added a commit
that referenced
this pull request
Nov 18, 2025
alvaromateo
added a commit
that referenced
this pull request
Nov 20, 2025
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.

Done
Add aliases section to snap details.
Design
Who is this intended for?
These changes are meant to be for users of snap packages.
Why are we doing this?
We want to give users a first glance at what they are installing in their machine.
Snaps are self contained packages invoked on the CLI by their name; but sometimes the snap name is different than the command name, so the snap has some aliases defined by default. These are the commands that the user of the snap will have available on their system to invoke the snap after installing it and currently there's no visibility of it (probably it will be information available on the documentation page of the snap, but it's left as a responsibility of the publisher to specify it).
What is the benefit to the user, and/or experience? To the business?
This change will give more information to the user of snap packages, by listing all the commands that are added to their system when installing the snap they are looking at.
How will we know if it worked?
This is a Quality of Life addition. I'm not sure how can we measure success for this type of change.
How to QA
Testing
Issue / Card
Fixes WD-17150