Hello InterSystems Team,
First of all, thank you for the excellent VSCode extension. It has greatly improved our development experience.
However, I am writing to report a critical risk regarding the default setting of objectscript.syncLocalChanges.
The Problem
Currently, the default value is set to all. In a team environment where developers use mixed tools (e.g., some use Studio, some use Git command line, others use VSCode), this setting is extremely dangerous.
Because it automatically syncs any local file change to the server, it frequently causes code to be overwritten or deleted without the developer realizing it. For example:
A developer runs git pullto update local files.
The extension detects a "file change" and immediately pushes the local state (which might not be the latest version intended for the server) to the public database.
Other developers' work is silently wiped out.
This issue occurs unpredictably ("like a stealth attack") and causes significant disruption to our team's workflow.
Proposed Solution
I strongly suggest changing the default behavior in the next release:
Change Default Value: Please change the default value from allto either none (safest, manual control) or vscodeOnly.
Auto-Recovery (Safety Net): For existing users who currently have allconfigured, please consider automatically migrating their setting to the new default when they upgrade. This would prevent users who are unaware of this setting from accidentally damaging the shared codebase.
Opt-in for all: Users who specifically require the allmode can still manually change it back. This ensures that only those who fully understand the risks are using it.
Why this matters
In an enterprise multi-user environment, allshould never be the default. Setting it to noneprotects the integrity of the public library and gives developers the necessary review space before pushing code.
Thank you for considering this request. We look forward to a safer default configuration!
Best regards
Hello InterSystems Team,
First of all, thank you for the excellent VSCode extension. It has greatly improved our development experience.
However, I am writing to report a critical risk regarding the default setting of objectscript.syncLocalChanges.
The Problem
Currently, the default value is set to all. In a team environment where developers use mixed tools (e.g., some use Studio, some use Git command line, others use VSCode), this setting is extremely dangerous.
Because it automatically syncs any local file change to the server, it frequently causes code to be overwritten or deleted without the developer realizing it. For example:
A developer runs git pullto update local files.
The extension detects a "file change" and immediately pushes the local state (which might not be the latest version intended for the server) to the public database.
Other developers' work is silently wiped out.
This issue occurs unpredictably ("like a stealth attack") and causes significant disruption to our team's workflow.
Proposed Solution
I strongly suggest changing the default behavior in the next release:
Change Default Value: Please change the default value from allto either none (safest, manual control) or vscodeOnly.
Auto-Recovery (Safety Net): For existing users who currently have allconfigured, please consider automatically migrating their setting to the new default when they upgrade. This would prevent users who are unaware of this setting from accidentally damaging the shared codebase.
Opt-in for all: Users who specifically require the allmode can still manually change it back. This ensures that only those who fully understand the risks are using it.
Why this matters
In an enterprise multi-user environment, allshould never be the default. Setting it to noneprotects the integrity of the public library and gives developers the necessary review space before pushing code.
Thank you for considering this request. We look forward to a safer default configuration!
Best regards