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

fix: activate extension after startup is finished #257

Merged
merged 1 commit into from
Mar 10, 2024

Conversation

byCedric
Copy link
Member

Linked issue

This is because workspaceContains:node_modules/expo doesnt work for non-top-level references.

See: microsoft/vscode#2739

This is because `workspaceContains:node_modules/expo` doesnt work for non-top-level references.

See: microsoft/vscode#2739
@byCedric byCedric merged commit fd07af8 into main Mar 10, 2024
18 checks passed
@byCedric byCedric deleted the fix/activation-events branch March 10, 2024 13:23
expo-bot pushed a commit that referenced this pull request Mar 10, 2024
## [1.4.2](1.4.1...1.4.2) (2024-03-10)

### Bug fixes

* activate extension after startup is finished ([#257](#257)) ([fd07af8](fd07af8))
* use proper vsix file name when adding to github release ([1b88b19](1b88b19))

### Code changes

* only re-fetch config when affected ([#256](#256)) ([f5a2986](f5a2986))
@expo-bot
Copy link
Contributor

🎉 This PR is included in version 1.4.2 🎉

The release is available on GitHub release

Your semantic-release bot 📦🚀

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

Successfully merging this pull request may close these issues.

2 participants