Skip to content
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

Collaborate or merge with TimeRange? #1

Open
schwern opened this issue Oct 1, 2024 · 1 comment
Open

Collaborate or merge with TimeRange? #1

schwern opened this issue Oct 1, 2024 · 1 comment

Comments

@schwern
Copy link

schwern commented Oct 1, 2024

I'm about to publish TimeRange. Our projects are remarkably similar. The goal of TimeRange is to have an object which can iterate by time intervals (not just seconds) without ActiveSupport. I chose a Range subclass because it got lots of features for free. I like your approach of extending Time good as well, but I'd prefer it was optional.

Would you be interested in collaborating and perhaps merging the projects?

@ixti
Copy link
Contributor

ixti commented Nov 9, 2024

Totally cool with that. As it's clear this project is pretty much abandoned, and judging by rubygems.org is not much used anyway. So we cut a release that depends on TimeRange with deprecation warning that people should switch (if anybody still using time iterator)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants