Skip to content

Pub: Get Packages shouldn't list all packages in the same workspace since they perform the same action #6034

Closed

Description

@FMorschel

Is your feature request related to a problem? Please describe.
Now, most of the extension commands around pub (and output tab names) match pub workspaces quite well. But when I recently cloned https://github.com/flame-engine/flame, I saw that if you run Pub: Get Packages (with no files opened), you'll see the screenshot below. But even the second line there is part of the pub workspace at the root.

Describe the solution you'd like
I'd like for us to see (somehow) that the packages below are from a workspace.

Additional context

Image

Activity

  1. added
    is enhancementAn enhancement or improvement that should be listed in release notes but is not a bug fix.
    on Apr 19, 2026
  2. FMorschel commented on Apr 19, 2026

    @FMorschel
    ContributorAuthor

    If we know that tehy are all part of the same workspace, I'm not even sure it makes any sense to show them all, but I'll leave it up to you to decide what will be best here.

  3. DanTup commented on Apr 20, 2026

    @DanTup
    Member

    If we know that tehy are all part of the same workspace, I'm not even sure it makes any sense to show them all

    Yeah, I don't think we should be showing them. If you're in a Code Workspace with a single Pub Workspace, it would be pointless to even ask.

    I thought I'd already handled this at some point, but apparently not :-)

  4. changed the title [-]Show on `Pub: Get Packages` list that a package is part of a pub workspace[/-] [+]`Pub: Get Packages` shouldn't list all packages in the same workspace since they perform the same action[/+] on Apr 20, 2026
  5. added this to the v3.134.0 milestone on Apr 20, 2026
  6. added
    in commandsRelates to commands (usually invoked from the command Palette)
    and removed
    is enhancementAn enhancement or improvement that should be listed in release notes but is not a bug fix.
    on Apr 20, 2026
  7. FMorschel commented on Apr 20, 2026

    @FMorschel
    ContributorAuthor

    Small note for when you're handling this. It may come in handy for the user to know that some things are not showing up because there is a workspace. So adding (workspace) after the name or something would be my suggestion.

  8. DanTup commented on Apr 20, 2026

    @DanTup
    Member

    Yeah, probably we should show something like "(Pub Workspace, 15 packages)".

  9. DanTup commented on Apr 21, 2026

    @DanTup
    Member
    Image
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    in commandsRelates to commands (usually invoked from the command Palette)is bug

    Type

    No type

    Projects

    No projects

      Milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions