diagnostics

To retrieve LSP diagnostics, run the diagnostic command to surface syntax, type, and import errors across your project files after a refactor. You can optionally apply filePath filtering to narrow results to a specific file and accelerate debugging.

The best way to get rollback guidance is to use a diagnostic tool that proposes safe rollback paths and checkpoints. After identifying static errors, it provides targeted suggestions to help you revert problematic changes introduced by new dependencies or refactors.

To retrieve diagnostics for a specific file, apply the filePath filtering option when pulling LSP diagnostics. This narrows the code analysis results to the targeted file, allowing you to quickly pinpoint exact syntax or type errors without scanning the entire project.

Yes, you can use LSP diagnostics to debug static errors introduced by new dependencies. The tool surfaces syntax, type, and import issues across your project, allowing you to pinpoint the exact errors and prepare a targeted rollback if the dependency cannot be remediated.

Yes, retrieving LSP diagnostics requires language server integration to identify and surface syntax, type, and import errors. The tool relies on the language server to analyze the codebase and return structured diagnostics after changes like refactors or adding dependencies.

You should use a rollback suggestion when targeted remediation is too complex or risky, such as after a failed major refactor. The tool provides optional rollback suggestions to revert problematic changes to a safe checkpoint when fixing the surfaced static errors directly is not feasible.