IMO users will be quite confused when they see the two command "Track Time" and "Submit Time", especially as they look nearly identical and perform exactly the same action.
I think we can simplify this by only keeping the "Track Time" command. When testing the extension to check if it is ready for release I noticed that I really missed the caching feature of the "Track Time" command when I was using the "Submit Time" command. One use case I could see here is when you want to track a time for yesterday for example, you might want to quit raycast to find out when you stopped working at that day and of course would want to keep the start data which you filled in before.
Also, caching does not interfere with any submission of attendances as they always get reset when you submit an attendance.
Suggested Changes
remove "Submit Time" command
rephrase description and readme of "Track Time" command
keep cache for "Track Time" command, maybe even include "End Time" for caching (you might want to quit raycast to quickly check whether your times are correct, this could include the end time)
What do you think about this @Boosteblume? We should decide about this before updating the PR at raycast.
IMO users will be quite confused when they see the two command "Track Time" and "Submit Time", especially as they look nearly identical and perform exactly the same action.
I think we can simplify this by only keeping the "Track Time" command. When testing the extension to check if it is ready for release I noticed that I really missed the caching feature of the "Track Time" command when I was using the "Submit Time" command. One use case I could see here is when you want to track a time for yesterday for example, you might want to quit raycast to find out when you stopped working at that day and of course would want to keep the start data which you filled in before. Also, caching does not interfere with any submission of attendances as they always get reset when you submit an attendance.
Suggested Changes
What do you think about this @Boosteblume? We should decide about this before updating the PR at raycast.