Skip to content

Conversation

@plemarquand
Copy link
Contributor

The swift package show-dependencies and swift package describe commands run on extension activation, and several extension features are gated behind their results. These were run with execSwift calls which show no progress in the VS Code UI.

The swift package show-dependencies command specifically could kick off a package resolution if the dependencies are missing, and for large packages this could take quite some time. As a result the extension could look like it was not activating.

Move these two commands into VS Code tasks that report their status in the progress bar, and let the user see the actual commands being run in the terminal.

Tasks

  • Required tests have been written
  • [ ] Documentation has been updated
  • Added an entry to CHANGELOG.md if applicable

The `swift package show-dependencies` and `swift package describe`
commands run on extension activation, and several extension features are
gated behind their results. These were run with `execSwift` calls which
show no progress in the VS Code UI.

The `swift package show-dependencies` command specifically could kick
off a package resolution if the dependencies are missing, and for large
packages this could take quite some time. As a result the extension
could look like it was not activating.

Move these two commands into VS Code tasks that report their status in
the progress bar, and let the user see the actual commands being run in
the terminal.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant