hovancik/stretchly

[Feature request]: Modify "Pause Breaks" options

Open

#1,462 opened on May 31, 2024

View on GitHub
 (5 comments) (3 reactions) (0 assignees)JavaScript (410 forks)batch import
enhancementhelp wanted

Repository metrics

Stars
 (3,892 stars)
PR merge metrics
 (Avg merge 3h 28m) (9 merged PRs in 30d)

Description

Version

  • I'm using version 1.15.1

Existing requests

  • I've checked Existing requests

Advanced Preferences

  • I've checked Advanced Preferences

What operating system are you using?

macOS

Operating System Version

macOS Sonoma 14.4.1

Problem description

Hello! Thanks for creating this super useful software :)

I was wondering if it's possible to change these times here?

I'd like to have additional options like:

  • 5 minutes
  • 10 minutes
  • 15 minutes

I did take a look at other requests and didn't find anything. I've checked README and also config.json but either the option to modify is there and I'm blind :) or it wasn't implemented.

Possible solution

I'd like to have additional options like:

  • 5 minutes
  • 10 minutes
  • 15 minutes

Alternative solutions

If adding additional options is not feasible then there could be entries in config.json to modify the default values.

Additional information

No response

Code of Conduct

  • I agree to follow this project's Code of Conduct

Contributor guide

Research direction
To implement this feature, first locate the pause break settings UI component in the source code (likely in an Electron window). The time options might be hardcoded in a dropdown or stored in configuration. Search for existing time constants or arrays. Add '5 minutes', '10 minutes', '15 minutes' to the list. If config.json is used, update the default configuration schema to include these. Ensure backward compatibility.
Tech stack
javascriptnodejs
Domain
desktopfrontend
Issue type
Feature
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
3
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.
Fresh
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
Clear
Prerequisites
Basic understanding of Electron appsFamiliarity with configuration files
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
70