mirror of
https://github.com/AppFlowy-IO/AppFlowy.git
synced 2026-03-24 12:56:59 +00:00
[GH-ISSUE #157] [Bug] Incorrect application folder name #83
Labels
No labels
2024
2025
2026
acct mgmt
AI
automation
bug
calendar
ci
CJK
cloud
code-block
collaboration
copy-paste
database
data migration
data sync
deploy
desktop
develop
develop
documentation
duplicate
editor
editor-plugin
emoji
export
files
flutter-only
follow-up
formula
good first issue for devs
good first issue for experienced devs
grid
hacktoberfest
HACKTOBERFEST-ACCEPTED
help wanted
i18n
icons
images
importer
improvements
infra
install
integrations
IR
kanban board
login
look and joy
mentorship
mobile
mobile
needs design
new feature
new feature
non-coding
notes
notifications
onboarding
organization
P0+
permission
platform-linux
platform-mac
platform-windows
plugins
program
pull-request
Q1 25
Q1 26
Q2 24
Q2 25
Q3 24
Q3 25
Q4 24
Q4 25
react
regression
rust
rust
Rust-only
Rust-only
Rust-starter
Rust-starter
self-hosted
shortcuts
side panel
slash-menu
sync v2
table
tablet
task
tauri
templates
tests
themes
translation
v0.5.6
v0.5.8
v0.5.9
v0.6.0
v0.6.1
v0.6.4
v0.6.7
v0.6.8
v0.7.1
v0.7.4
v0.7.4
v0.7.5
v0.7.6
v0.7.7
v0.7.8
v0.8.0
v0.8.4
v0.8.5
v0.8.9
web
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
AppFlowy-IO/AppFlowy#83
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
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:
Expected behavior
The folder should be called "AppFlowy" or "appflowy)
Screenshots

Desktop (please complete the following information):
Additional context
The folder name is hard coded. Maybe this should be in the translation files?
@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.
@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.
@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.
@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?
@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.
@annieappflowy commented on GitHub (Jun 12, 2023):