You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Describe the bug
Scripts that get checked out in Script Studio have their name automatically converted to all lower-case. This causes anyone migrating from Script Studio to WIDE to get "symbol already defined" error due to inconsistent names of scripts.
To Reproduce
Create a project using REDkit
Use Script Studio to check out a script file that originally in content0 contains any upper-case letters in its name. This operation should result in import of this file, but with name all in lower-case.
Open the project in WIDE
Observe "symbol already defined" errors popping up due to difference in colliding script paths
Expected behavior
Casing of files should be ignored in script path resolution.
Additional context
This lower-casing operation seems to happen in script compiler's backend, as error messages printed from compilation always show scripts with their names all in lower case.
The text was updated successfully, but these errors were encountered:
Describe the bug
Scripts that get checked out in Script Studio have their name automatically converted to all lower-case. This causes anyone migrating from Script Studio to WIDE to get "symbol already defined" error due to inconsistent names of scripts.
To Reproduce
Expected behavior
Casing of files should be ignored in script path resolution.
Additional context
This lower-casing operation seems to happen in script compiler's backend, as error messages printed from compilation always show scripts with their names all in lower case.
The text was updated successfully, but these errors were encountered: