Showing content from https://github.com/vuejs/vetur/issues/800 below:
Centralize all file system access in VLS · Issue #800 · vuejs/vetur · GitHub
Motivation
Currently Vetur's file system access is scattered throughout the code. However, we also use TextDocuments from https://github.com/Microsoft/vscode-languageserver-node to track LSP documents, and with the new FileEvents generated through VS Code file watcher, it's time to put these all together.
Benefits
- All file access / events in one place. Easier to track, log, do perf analysis, etc
- Possible to use in-memory / virtual FS system with VLS
- Easier to manage the "virtual files" we generate for each region in Vue files
- Possible to reduce chattiness of LSP by switching to Incremental Syncing
- Possible to listen to changes by granularity of Vue regions (as compared to currently letting each file change triggering all features in file)
Fixes
Unblocks
RetroSearch is an open source project built by @garambo
| Open a GitHub Issue
Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo
HTML:
3.2
| Encoding:
UTF-8
| Version:
0.7.4