Skip to content
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

Extension requires reload to activate after first tests.ps1 file #122

Closed
fflaten opened this issue Apr 1, 2022 · 5 comments · Fixed by #169
Closed

Extension requires reload to activate after first tests.ps1 file #122

fflaten opened this issue Apr 1, 2022 · 5 comments · Fixed by #169
Labels
enhancement New feature or request

Comments

@fflaten
Copy link

fflaten commented Apr 1, 2022

The current activationevent for *.tests.ps1 in the workspace doesn't trigger on new file. You need to reload windows after the first test-file exists. Any way to make it look again on file creation and/or rename?

@fflaten
Copy link
Author

fflaten commented Apr 1, 2022

Probably depends on microsoft/vscode#28122.
Maybe mention reload-requirement in the readme while we wait? 🙂

@JustinGrote
Copy link
Collaborator

@fflaten good tip. As an alternative, they now have an option to lazy-load an extension, so we could lazy-load and have a minimal filesystem watcher.

@JustinGrote JustinGrote added the enhancement New feature or request label Jul 26, 2023
@JustinGrote
Copy link
Collaborator

@fflaten warning added to README in 6e64003

@fflaten
Copy link
Author

fflaten commented Jul 27, 2023

Thanks. Close issue or leave open for lazy load or new activationevent?

@JustinGrote
Copy link
Collaborator

Leaving open for the lazy load activation to be implemented.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants