brandonsoto/pomodoro-timer

:tomato: A Pomodoro Timer extension for VSCode

Brandon Soto 👨‍💻

Senior Software Engineer at Elektrobit

data class SoftwareEngineer(val name: String, val knowledge: Knowledge, val education: String)
data class Knowledge(val languages: List<String>, val operating_systems: List<String>, val dev_ops: List<String>)

val brandon = SoftwareEngineer(
    name = "Brandon Soto",
    knowledge = Knowledge(
        languages = listOf("Kotlin/Java", "C++", "Python", "Javascript"),
        operating_systems = listOf("Android", "RedHat", "Ubuntu", "QNX"),
        dev_ops = listOf("Docker", "Ansible", "AWS")
    ),
    education = "B.S. Computer Science"
)

I'm an engineer whose written code on defensive countermeasure and infotainment systems. I currently bring CarPlay and Android Auto to your car!

---

pomodoro-timer's Issues

Finalize user commands

The user commands should be as follows:

1. start - starts/resumes the timer but does not reset it
2. stop - pauses the timer but does not reset it
3. reset - stops and resets the timer but does not start it

Implement unit tests

Need to write unit tests for the PomodoroTimer class.

Format time correctly

Time is not currently formatting correctly in the status bar. The format should be 00:00.

Pressing restart does not cause a restart

Pressing the restart button will not restart the timer if it's already running.

Create marketplace icon

Need an icon for the marketplace.

Hide stop functionality from users?

Having stop and pause functionality is a tad confusing. Should stop() just be used internally? Maybe replace it with restart functionality?

Write unit tests

Need unit tests for the entire Pomodoro class.

Update README

The README is still the template provided by yeoman. This will need to be updated fully before release.

Pomodoro preferences do not show up

The extension's preferences do not currently show up in the settings. This needs to be fixed ASAP.

User needs to restart VSCode in order for preferences to update

Pomodoro currently requires a restart of VSCode if the user changes Pomodoro's configuration. This should not be the case. It should be able to update on the fly.