mirror of
https://github.com/BoostIO/BoostNote-App.git
synced 2026-04-26 21:05:55 +03:00
[GH-ISSUE #1009] No way to move a nested folder into the top level workspace #445
Labels
No labels
android 🤖
assigned to core 🦹
bug 🐛
documentation 📚
documentation 📚
duplicate 🚫
external issue 🔼
external issue 🔼
feature request 🌟
funded on issuehunt 💵
help wanted 🆘
improvement request 🔨
improvement request 🔨
ios 🍎
mobile 📱
needs investigation 🔬
needs more info ℹ️
needs specs 📐
plugin idea 🔌
plugin idea 🔌
poll 🗳️
pull-request
question ❓
rewarded on issuehunt 🎁
security issue 🔑
won’t fix ❌
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/BoostNote-App#445
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 @bowenli on GitHub (Jun 16, 2021).
Original GitHub issue: https://github.com/BoostIO/BoostNote-App/issues/1009
Originally assigned to: @Rokt33r on GitHub.
Current behavior
If you make a nested folder, there is no drag area to put that folder into the top level workspace.
Expected behavior
Able to drag nested folder into the top level workspace so it is no longer nested.
Steps to reproduce
Environment
Desktop/Web
@Komediruzecki commented on GitHub (Jun 16, 2021):
Hi, bowenli,
Just letting you know that there is already work done on this, hopefully next release will include ordering of the sidebar items, which will allow moving a folder to workspace root as well.
Thank you for your patience!
@Komediruzecki commented on GitHub (Aug 19, 2021):
Just to note that I was talking about local spaces, the latest release of the local space desktop application should be able to do anything on top-level as well.
Cloud space probably doesn't have this but it is being worked on.
@Rokt33r commented on GitHub (Aug 23, 2021):
Although we really want to resolve this issue, we should need quite more time to fix it. Although we are showing the top-level folders as normal folders, we are still handling them differently in the backend. So please wait a bit more until we fix the backend data structure.