Skip to content
This repository has been archived by the owner on Jul 15, 2023. It is now read-only.

Activate extension when workspace contains go files #2859

Merged
merged 1 commit into from
Nov 19, 2019
Merged

Activate extension when workspace contains go files #2859

merged 1 commit into from
Nov 19, 2019

Conversation

zmb3
Copy link
Contributor

@zmb3 zmb3 commented Oct 22, 2019

Fixes #2821

package.json Outdated
@@ -66,6 +66,7 @@
"vscode": "^1.30.0"
},
"activationEvents": [
"workspaceContains:**/.go",
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Shouldn't this be:

Suggested change
"workspaceContains:**/.go",
"workspaceContains:**/*.go",

Otherwise it will only activate, if it finds a literal .go file.
I wanted to open a PR myself and this happened to me during testing, when omitting the asterisk in the globbing pattern.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

🤦‍♂️oops, thanks @ToothlessGear

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

extension does not eager load when workspace contains .go files
3 participants