feature: use vscode.workspace.fs API to load Expo projects
#252
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
expo-bot
pushed a commit
that referenced
this pull request
Mar 8, 2024
## [1.4.0](1.3.0...1.4.0) (2024-03-08) ### New features * use `vscode.workspace.fs` API to load Expo projects ([#252](#252)) ([5a596d1](5a596d1)) ### Code changes * add tests and replace minimatch with picomatch ([#248](#248)) ([519d179](519d179)) ### Other chores * bump all workflow actions to latest versions ([#250](#250)) ([5a4bf25](5a4bf25)) * bump minimal required vscode version ([#249](#249)) ([6c789b8](6c789b8)) * enable tests for vscode insiders versions ([#253](#253)) ([036af2b](036af2b)) * use composite action to resolve exact npm package version ([#251](#251)) ([2d0efa6](2d0efa6))
|
🎉 This PR is included in version 1.4.0 🎉 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
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Linked issue
We already used most of the
vscode.workspace.fsAPI, but not to load Expo projects. That still happened throughfs.calls. This fully removes allfs.calls when loading Expo projects.