How to troubleshoot VSCode extension? Package not appearing in workspace.
I have VS Code with extensions connected to IRIS for Health. One top-level ObjectScript package is not displayed in the workspace for this namespace. This package exists in the namespace and is visible in SMP. If I create a new class with a different top-level package name (package that didn't previously exist) it will immediately appear in the workspace.
Is there any debug logging I can enable to look for errors or do any other troubleshooting?
Forgot to mention: the missing package is custom, not a system package.
Comments
@Marc.MundtCan you post your workspace configuration (the .code-workspace file if you're using server-side editing)? Do you see any errors in the ObjectScript Output channel? Does the package only contain system or generated classes? By default those are not shown.
No errors are appearing in the OUTPUT tab.
The package contains only custom classes.
Not sure if this is the right config -- let me know if not. I'm on Linux and this is ".config/Code/Workspaces/1731519734832/workspace.json" The problematic item is irishealth:CVSCCDA.
{
"folders": [
{
"name": "irishealth:AUTOMATION",
"uri": "isfs://irishealth:automation/"
},
{
"name": "irishealth:FHIRCONVERSION",
"uri": "isfs://irishealth:fhirconversion/"
},
{
"name": "irishealth:%SYS",
"uri": "isfs://irishealth:%sys/"
},
{
"name": "irishealth:CVSCCDA",
"uri": "isfs://irishealth:cvsccda/"
}
]
}
@Marc Mundt I'll reach out to you privately.
This turned out to be a bug in VS Code core. The issue report can be found here: https://github.com/microsoft/vscode/issues/239350
We tracked this down to a core VS Code setting that filters out certain subdirectory names. Removing the entry in this list for "CVS" solved the problem.
.png)