Imported File Selection Should Strictly Use Windows Path — Root / Path Causes Errors #16138
Unanswered
sumit140792
asked this question in
General
Replies: 1 comment
-
Hey @sumit140792, please file a bug report for this. |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
-
Description:
When importing a required file (e.g., configuration, data, or workspace-related files), the file selection dialog allows selecting from the root / directory, even on Windows systems. This leads to incorrect path resolution, import errors, and overall bad user experience.
Expected Behavior:
On Windows, the file import dialog should:
Use Windows-style paths (e.g., C:\Users\Username...)
Strictly prevent or not allow defaulting to root / paths, which are invalid in the Windows file system.
Actual Behavior:
File selection opens at or allows navigating to /.
If a file is selected from this path, the application may:
Crash or throw an exception
Fail to import the file correctly
Misinterpret the file path or structure
Steps to Reproduce:
Launch the app on Windows.
Attempt to import a required file (via “Import”, “Add Config”, etc.).
Notice that the file dialog may start at /, or allow manual entry of root-style paths.
Selecting or entering such a path causes errors.

Beta Was this translation helpful? Give feedback.
All reactions