codespent / autoggl

VSCode extension to automatically track your time in workspaces to Toggl projects.

Hi, I'm Patrick

A Full Stack developer with deep interest in DX Tooling, DevOps & Artificial Intelligence.

name: Patrick Hanford
about: |
  Fullstack Developer with interest in DevOps & Artifical Intelligence.  
located_in: Michigan, USA
title: Full-Stack Developer

interests:
  [
    "DevOps",
    "Web Development",
    "APIs",
    "UI/UX",
    "Data Science",
    "Machine Learning",
    "Artificial Intelligence",
    "IoT"
  ]

professional_experience:
  [
    "4 years @ Robert Half"
    "2 years @ StreamKick",
  ]

products_launched:
  [
    "DevStreams.io",
    "Bias Agnostic Framework Library"
  ]

autoggl's Issues

Timer not always starting when opening new folder from active window

If working in WorkspaceA and you switch to WorkspaceB, there's a chance that the timer will not automatically start.

startTimer fails if user has 0 existing Toggl projects

startTimer fails if user has 0 existing Toggl projects likely due to fetching user's projects to map over.

'Set Client' command

Add a command called Autoggl: Set Client that allows the user to set the client from the command palette for the current project.

Detect idle time to pause timer

If the project is left open, but user has stepped away from their PC, the timer will continue even after the OS has idled.

We need a way to help in some way to get accurate "working" time rather than just time the project has been open.

Timer doesn't stop when VSCode isn't explicitly "deactivated"

stopTimer is only run on deactivated hook which implies the user manually closed the window.

If the window is left open when the device is shut down, or VSCode is force closed through a task manager, then the deactivated method never runs, and the timer continues.

Need a way to handle this to avoid inaccuracies with timing.

Add contribution guidelines

Add contributing guidelines to README and explore ways to improve the dev experience.

Initial thoughts for sanity:

• Add health files to help new contributors
• Add commitizen for commit consistency
• Use Husky for eslint/prettier for style consistency
• Add steps for debugging VSCode extensions to README