You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
full-analysis: auto-instantiate environments and cache detection results
Add automatic `Pkg.instantiate()` for environments that have not been
instantiated yet (e.g., freshly cloned repositories or new project
directories). This allows full analysis to work immediately upon opening
files in such environments, whether they are package source files,
test files, or scripts with their own Project.toml.
Also add caching for environment detection results to avoid redundant
`Pkg.instantiate()` calls and `Base.identify_package_env` lookups for
the same environment.
The behavior is controlled by `full_analysis.auto_instantiate` config
option (default: `true`).
Copy file name to clipboardExpand all lines: jetls-client/package.json
+5Lines changed: 5 additions & 0 deletions
Original file line number
Diff line number
Diff line change
@@ -119,6 +119,11 @@
119
119
"default": 1,
120
120
"minimum": 0,
121
121
"markdownDescription": "Debounce time in seconds before triggering full analysis after a document change."
122
+
},
123
+
"auto_instantiate": {
124
+
"type": "boolean",
125
+
"default": true,
126
+
"markdownDescription": "When enabled, JETLS automatically runs `Pkg.instantiate()` for packages that have not been instantiated yet (e.g., freshly cloned repositories). This allows full analysis to work immediately upon opening such packages. Note that this will automatically create a `Manifest.toml` file when the package has not been instantiated yet."
0 commit comments