Cache BuildPlan
in LSP
#5462
Labels
enhancement
New feature or request
forc-pkg
Everything related to the `forc-pkg` crate.
language server
LSP server
In an offline chat with @FuelLabs/tooling, it is stated that LSP spends considerable amount of time while dealing with build plan generation as forc-pkg does not offer an in memory representation for manifest files (it expects to read them from disk). One option is refactoring forc-pkg such that we can give it a in-memory manifests instead to remove expensive I/O operations. Although this might be a good refactor in the future, we realized that we can actually cache the build plan entirely for LSP purposes as the build plan won't be changing in any type of key stroke (other than the ones being appleid to a manifest file for the current workspace/project). So we can cache it entirely and do not need to regenerate for each keystroke.
The text was updated successfully, but these errors were encountered: