Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Separate clock-in and clock-out fields #650

Open
3 tasks done
adrianjav opened this issue Dec 2, 2024 · 0 comments
Open
3 tasks done

Separate clock-in and clock-out fields #650

adrianjav opened this issue Dec 2, 2024 · 0 comments
Labels
enhancement New feature or request

Comments

@adrianjav
Copy link

⚠️ Please check that this feature request hasn't been suggested before.

  • I searched previous Issues didn't find any similar feature requests.
  • I am only requesting a single feature. Multiple changes should be split into individual requests, with links between them.
  • I believe my requested feature will be generally applicable to other users, not just me: it is not uniquely tied to my personal workflow.

🔖 Feature description

I love the new time-tracking feature! And since it is still an experimental feature, I thought I could add my two cents.

In short, I would appreciate if we could have separate dataview fields for clocking in and out ([clock-in:: in] and [clock-out:: out]) for each task, rather an a single field of the form [clock:: in--out].

✔️ Solution

The solution would come down to change the logic to deal with two different fields for clocking in and out, rather than having a single field for both functionalities.

Why this change? Essentially, this would make it easier to parse tasks later on when we try to create scripts for user-specific needs.

For example, if I want to compute how much time I've spent in certain tasks, I could directly gather the clocking ins and outs as dataview's time fields and compute their difference, rather than first having to parse them as a single string and split them by the '--' separator.

❓ Alternatives

The alternative would be to leave the users to go through an initial extra parsing step to obtain the two clocking times, so if there is any clear disadvantage code-wise on doing this over having a single field feel free to ignore the request.

📝 Additional Context

PS: I am not familiar with typescript. I am sorry I cannot be more specific with the necessary code changes.

@adrianjav adrianjav added the enhancement New feature or request label Dec 2, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

1 participant