Hi @Brett Saviano 

We have been doing further testing and have come across an issue. In our environment, we have various git hooks setup to configure certain IRIS globals when classes change. Without this, the compile will fail for some generated classes.

What happens now is, when you git pull, this extension detects the file system changes and attempts to compile the classes before the git hook has completed, causing errors to be reported. Looking at the logs, I can see VSCode attempted to compile a few seconds before the git hook completed.

To resolve this, please would you consider adding a "Seconds to Delay Local Sync for External Changes" setting? We could then set it to 10 or whatever and it would wait that amount of time after a file system change before attempting a compile.

There is no need to delay the compile when saving directly in VS Code so the setting should either only be for external changes, or have two delay settings, one for internal and another for external. We'd be happy with just a delay for external changes.

Thanks.

Michael

I have been testing these changes and like them very much, especially the monitoring of the file system which means discards/stashes via external tools now work (code is recompiled).

However, I'm not a fan of this change:

Change the default value of the objectscript.autoAdjustName setting to false. Now that we have an index of the workspace, we no longer require that a document's name match the file path for the extensions to find it.

It means when creating a brand new objectscript routine it is now missing the header and therefore invalid. It took me a while to find the setting and re-enable it. Did you really mean to stop new routines from auto inserting a valid header?

To clarify, the Atelier preview will only work with Unicode servers. That is not permanent. Atelier WILL support 8-bit servers in future.