[GH-ISSUE #157] [Bug] Incorrect application folder name #83

Closed
opened 2026-03-23 20:31:36 +00:00 by mirror · 6 comments
Owner

Originally created by @MikeWallaceDev on GitHub (Dec 15, 2021).
Original GitHub issue: https://github.com/AppFlowy-IO/AppFlowy/issues/157

Originally assigned to: @appflowy on GitHub.

Describe the bug
The application creates a directory in the user's "Document" directory called "flowy". As per application conventions the directory should be called "AppFlowy" (ideally), or "appflowy" if you don't want caps in a directory name.

To Reproduce
Steps to reproduce the behavior:

  1. Install and run the application
  2. Look in your Documents directory
  3. Find the "flowy" folder
  4. See error

Expected behavior
The folder should be called "AppFlowy" or "appflowy)

Screenshots
image

Desktop (please complete the following information):

  • OS: Linux/All
  • Browser N/A
  • Version 0.0.2

Additional context
The folder name is hard coded. Maybe this should be in the translation files?

Originally created by @MikeWallaceDev on GitHub (Dec 15, 2021). Original GitHub issue: https://github.com/AppFlowy-IO/AppFlowy/issues/157 Originally assigned to: @appflowy on GitHub. **Describe the bug** The application creates a directory in the user's "Document" directory called "flowy". As per application conventions the directory should be called "AppFlowy" (ideally), or "appflowy" if you don't want caps in a directory name. **To Reproduce** Steps to reproduce the behavior: 1. Install and run the application 2. Look in your Documents directory 3. Find the "flowy" folder 4. See error **Expected behavior** The folder should be called "AppFlowy" or "appflowy) **Screenshots** ![image](https://user-images.githubusercontent.com/5375835/146252918-bd499cd8-bbbe-4e53-90b6-87260c066837.png) **Desktop (please complete the following information):** - OS: Linux/All - Browser N/A - Version 0.0.2 **Additional context** The folder name is hard coded. Maybe this should be in the translation files?
mirror 2026-03-23 20:31:36 +00:00
Author
Owner

@skutter-de commented on GitHub (Jul 20, 2022):

Since the content of the folder is not really human readable, I think the path should be switched to ~/.local/share/appflowy as per XDG specification (https://wiki.archlinux.org/title/XDG_Base_Directory) (there is a link to the full spec on the wiki page).
This would also help with Flatpak support in the future since you don't need to have permission to write to Documents this way.
Applications shouldn't be writing their human-unreadable data to a visible folder, the directory layout is designed to you don't have to use your Documents folder for anything but actual Documents.

<!-- gh-comment-id:1189921909 --> @skutter-de commented on GitHub (Jul 20, 2022): Since the content of the folder is not really human readable, I think the path should be switched to ~/.local/share/appflowy as per XDG specification (https://wiki.archlinux.org/title/XDG_Base_Directory) (there is a link to the full spec on the wiki page). This would also help with Flatpak support in the future since you don't need to have permission to write to Documents this way. Applications shouldn't be writing their human-unreadable data to a visible folder, the directory layout is designed to you don't have to use your Documents folder for anything but actual Documents.
Author
Owner

@annieappflowy commented on GitHub (Jul 20, 2022):

Thanks @Gaming4LifeDE for sharing the knowledge and suggesting a change. We'll evaluate it and consider your suggestions.

<!-- gh-comment-id:1190220492 --> @annieappflowy commented on GitHub (Jul 20, 2022): Thanks @Gaming4LifeDE for sharing the knowledge and suggesting a change. We'll evaluate it and consider your suggestions.
Author
Owner

@MikeWallaceDev commented on GitHub (Jul 27, 2022):

Hello :) Just to say that I don't agree with this, no data in the document folder is meant to be human readible (or maybe I don't understand what you mean by "human readable"). It's application data. It's your saved files. Those files could be in binary...

The stuff that we put in the flowy folder is user data, and the user has to know about this so that they can back it up.

I'm not saying that we are doing it perfectly. But I am saying that the user needs to be aware of this data.

<!-- gh-comment-id:1196881138 --> @MikeWallaceDev commented on GitHub (Jul 27, 2022): Hello :) Just to say that I don't agree with this, no data in the document folder is meant to be human readible (or maybe I don't understand what you mean by "human readable"). It's application data. It's your saved files. Those files could be in binary... The stuff that we put in the flowy folder is user data, and the user has to know about this so that they can back it up. I'm not saying that we are doing it perfectly. But I am saying that the user needs to be aware of this data.
Author
Owner

@polypixeldev commented on GitHub (Jul 29, 2022):

I think that for now it's fine to leave it in the documents directory (and rename it to "appflowy"). However, in the future I think that the user should be given full control over where the data is stored. There would probably still need to be a global config file (in .config or somewhere that's appropriate) that has a hardcoded path so that it can know where the user chose to store the data.

Edit: For Windows the global config file could go somewhere in AppData maybe?

<!-- gh-comment-id:1199823397 --> @polypixeldev commented on GitHub (Jul 29, 2022): I think that for now it's fine to leave it in the documents directory (and rename it to "appflowy"). However, in the future I think that the user should be given full control over where the data is stored. There would probably still need to be a global config file (in .config or somewhere that's appropriate) that has a hardcoded path so that it can know where the user chose to store the data. Edit: For Windows the global config file could go somewhere in AppData maybe?
Author
Owner

@appflowy commented on GitHub (Aug 2, 2022):

@Poly-Pixel Yes, you're right. We will support users to choose their stored path in the future. So I think just leave it there for the moment.

<!-- gh-comment-id:1201923244 --> @appflowy commented on GitHub (Aug 2, 2022): @Poly-Pixel Yes, you're right. We will support users to choose their stored path in the future. So I think just leave it there for the moment.
Author
Owner

@annieappflowy commented on GitHub (Jun 12, 2023):

image Done
<!-- gh-comment-id:1587154307 --> @annieappflowy commented on GitHub (Jun 12, 2023): <img width="775" alt="image" src="https://github.com/AppFlowy-IO/AppFlowy/assets/12026239/f51f5ff7-8bdc-499c-b609-a9cc835c706e"> Done
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
AppFlowy-IO/AppFlowy#83
No description provided.