Skip to content

feat: provide option to exclude path for "run pub get" on outdated packages #4581

@Luckey-Elijah

Description

@Luckey-Elijah

Is your feature request related to a problem? Please describe.
When opening VS Code in a multi-package workspace, I do not want the message

Some packages are missing or out of date, would you like to get them now?

to appear for a specified path or glob.

Additional context
I use mason for generating dart packages in my workspace, but the package template is in the workspace so it is evaluated in the check for

[ ... ] [General] [Info] Found 1 folders requiring "pub get" or "pub upgrade":

But this is an issue since the package template itself is an invalid dart package. It might include characters like {, }, (, and ) in the pubspec.yaml's nameand in the package's path.

In my project I would specifically like the ability to exclude a glob like bricks/*/__brick__/** to align with my analysis file.

Metadata

Metadata

Assignees

No one assigned

    Labels

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

    Type

    No type

    Projects

    No projects

    Milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions