You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Describe the solution you'd like
I have deep directory paths, ending in something like .../projects/[project]/[taskNote]. However, currently the project will group by one of the first directories instead of [project]. It would therefore be very nice to have a toggle or define the depth of the directory to group by. For example, having 1, would select [project] as it's its parent directory, 2, would select projects its grandparent and so forth.
Describe alternatives you've considered
Currently I've made two rather crude edits to accomplish this, in the function parseFolderFromPath I've added:
Describe the solution you'd like
I have deep directory paths, ending in something like
.../projects/[project]/[taskNote]
. However, currently the project will group by one of the first directories instead of[project]
. It would therefore be very nice to have a toggle or define the depth of the directory to group by. For example, having 1, would select[project]
as it's its parent directory, 2, would selectprojects
its grandparent and so forth.Describe alternatives you've considered
Currently I've made two rather crude edits to accomplish this, in the function
parseFolderFromPath
I've added:and in the function
splitHeading
I've added:However, these overrule the current implementation. The simple solution is thus instead a toggle between this or the current implementation.
The text was updated successfully, but these errors were encountered: