-
Notifications
You must be signed in to change notification settings - Fork 116
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
Allow abbreviated time units (e.g. 30s, 5m, 1h, 3d) #144
Comments
I know this is super old, but it probably belongs as a feature request on chronic where it could potentially be useful to many more people than just those using Timetrap. Edit: maybe not such a good suggestion as Chronic's master branch hasn't moved in years. |
Indeed, it wasn't updated for a while. Also this PR is very useful for |
Totally. It's just that right now this gem does zero time parsing, and maybe that's an intentional choice. |
I do have some hesitation about adding additional natural time parsing directly to the timetrap gem. In theory it could be a convenient addition but it does open the door for a lot of potentially confusing bugs or behaviors. Another approach that occurred to me would be to add some kind of middleware layer to the CLI. This would be similar to the custom formatters (but on the input side) and give timetrap users a way to write code that would pre-process their command line input and allow extensibility like what's described in this issue. I don't have time these days to add any significant new features, but if someone was interested in exploring that approach, I'd be interested in pull requests. |
Where has it all gone? Mine used to be more abundant as well.
I'm somewhat interested. Not promising anything... |
Examples:
Prototype:
The text was updated successfully, but these errors were encountered: