VSCode Playground
General debugging strategy
- Check Discord (#announcements channel) / Github for any known issues
- Close the playground and reopen it
- Try reloading the entire window by pressing
Ctrl + Shift + P
orCmd + Shift + P
and typingDeveloper: Reload Window
- Ensure your VSCode Extension for BAML is up-to-date (It should should it its up-to-date in the Extensions tab in VSCode)
![](https://fdr-prod-docs-files-public.s3.amazonaws.com/https://boundary.docs.buildwithfern.com/2024-09-05T23:19:36.939Z/assets/images/docs_latest/vscode/extension-status.png)
- If nothing works, please file an issue on Github, ideally with a screenshot of the error and the steps to reproduce it.
Common Issues
No code lens in BAML files
This can happen in two cases:
-
You have syntax error in some
.baml
file. You can check the error in theProblems
tab in VSCode or running thegenerate
command in the terminal (See Generate) -
BAML extension is broken. Please try the tools above!
BAML extension is not working
Tests hanging
We’ve seen sparse repros of this, but closing the playground and reopening it should fix it.
Tests failing to run
You can debug the actual network request being made by BAML by opening developer tools:
![](https://fdr-prod-docs-files-public.s3.amazonaws.com/https://boundary.docs.buildwithfern.com/2024-09-05T23:19:36.939Z/assets/images/docs_latest/vscode/dev-tools.png)
BAML Client Generation Disabled
This means your generator
clause in your BAML file is out of sync with the version of the BAML extension you have installed. See Generate for more details.