When running scripts or commands in different environments, the issue of forward vs. backward slashes in file paths is causing compatibility problems.
Specifically, commands that involve file paths fail in Windows due to the difference in how slashes are handled (/ in Mac/Linux vs. \ in Windows). This affects both environmental variables and file paths during document export and other processes.
Proposed Fix:
Implement logic in the codebase to handle path normalization, converting file paths appropriately based on the operating system.
This could be handled by adding a utility function to convert between forward and backward slashes dynamically, depending on the environment in which the code is running.
Problem Zip file export bug:
When exporting the document model into a ZIP file, the exported ZIP is often corrupted or fails to work properly, particularly because the ZIP compression format used during the export process is incompatible with certain environments (Windows, Mac, Linux).
The problem is more prevalent on Windows systems, where the ZIP format generated from the export differs from the one Connect expects.
Problem (Forward/Backward Slashes):
When running scripts or commands in different environments, the issue of forward vs. backward slashes in file paths is causing compatibility problems. Specifically, commands that involve file paths fail in Windows due to the difference in how slashes are handled (/ in Mac/Linux vs. \ in Windows). This affects both environmental variables and file paths during document export and other processes.
Proposed Fix:
Implement logic in the codebase to handle path normalization, converting file paths appropriately based on the operating system. This could be handled by adding a utility function to convert between forward and backward slashes dynamically, depending on the environment in which the code is running.
Problem Zip file export bug:
When exporting the document model into a ZIP file, the exported ZIP is often corrupted or fails to work properly, particularly because the ZIP compression format used during the export process is incompatible with certain environments (Windows, Mac, Linux). The problem is more prevalent on Windows systems, where the ZIP format generated from the export differs from the one Connect expects.