-
Notifications
You must be signed in to change notification settings - Fork 377
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
New File dialog is overly non-standard #2972
Comments
@liweitian can you take a look at this please? In addition to @tomlm's Expected behavior, please also do the following:
Directories with special prefixes like '$' or '.' should be filtered out. |
@cwhitten we were kind of trying to unify the path in unix style to make it more convininent. So we are now getting to have different UI in win vs non-win, right? that could solve 1 and 3 in @tomlm's request. And @tomlm, for 2, i see the default folder is C:\user\myusername\documents\Composer |
I like the consistency of the unix path for internal operations. We can maintain that if it is helpful. When we render the view can we consider a transform to the os path separator? This wouldn't require a change to the internal model of path serialization. The request is to default to |
Sorry for not following up this quickly, i saw this is closed, Our previous our default path is /Users/{username}/Documents/Composer, and now we updated to /User/{username}, which i don't think it's the stardard, @cwhitten @tomlm . From what i know, most application write to /Users/{username}/Documents/{appId} like VS, and Github desktop, IIS, and so on, for example I thought this is the convention. And there are a few application do write directly into /User/{username}, but they at least use a {appID} instead of create many folder's there, which is annoying and definitely not the standard So i think we need to at least have an app identifier like composer, /User/{username}/{appID}, instead of directly writing to /User/{username}. I prefere /User/{username}/Documents/{appID} if possible. |
Describe the bug
I installed from github release page (0.0.1)
Version
0.0.1 (2 days ago)
Browser
OS
To Reproduce
Expected behavior
Screenshots
Additional context
The text was updated successfully, but these errors were encountered: