manrajgrover/organize-cli

Organize by time doesn't end up as timeline, if running on different days

Open

#31 opened on Nov 2, 2017

View on GitHub
 (1 comment) (1 reaction) (0 assignees)JavaScript (13 forks)github user discovery
feature requesthelp wanted

Repository metrics

Stars
 (370 stars)
PR merge metrics
 (PR metrics pending)

Description

I don't know the intention of the -d option, but i would like to organize my downloads as followed.

downloads of day 1 # organize runs day 1
downloads of day 2 # organize runs day 2
downloads of day 3 # ...

With every run for a day the timeline gets a new entry. I couldn't find a way to do this just with running organize-cli. At the moment i will end up with:

# run organize day 1
day 1

# run organize day 2
day 2
   --> day 1

# run organize day 3
day 3
   --> day 2
           --> day 1

# sorry for the creepy tree

This means older folders gets nested into the newer one each day. Maybe there could be an option for the use-case of creating an timeline in an folder. I hope my issue is clear. Please correct me, if i misunderstand something. Regardless of your answer, this tool is awesome and made my day. Thank you

Contributor guide

Research direction
Investigate the logic for creating date based folders when organizing files. The current implementation nests folders instead of creating separate folders for each day. Trace the code path that determines folder creation and modification.
Tech stack
javascript
Domain
cli
Issue type
Bug
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
2
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
1-3 hours
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
Active
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
Clear
Prerequisites
GitNode.js
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
75