The
language server answers questions about an mz-deploy project's object
graph. Use the LSP tool for these instead of text search — grep finds strings that look
like an object name, the language server finds the object.
Before changing an object, use these to find what depends on it. In Materialize a view's
definition constrains everything downstream of it, so an edit that type-checks in
isolation can still break dependents.
Parse errors surface automatically after each edit. Treat them as authoritative for
syntax; they come from the same parser
uses to build the project.
must be on
(
). If every navigation request comes back
empty while the server looks healthy, the plugin's
mz-deploy project directory
setting is pointing somewhere other than the directory holding
. The
server takes that directory as its project root, and a project nested in a subdirectory
needs the setting to name that subdirectory. Report this rather than falling back to
grep — a stale setting is worth fixing once.