Add support for "ly"

[fega]

like "monthly"
"weekly"
etc :)

[sampathBlam]

@fega , @simison : Hi. Can you provide a sample usecase which would be solved by adding 'ly' support to human interval?
With respect to agenda, I could not think of any, as agenda already has .every and similar interval based time configurations for scheduling tasks.
I understand that agenda is not the only package that depends on human-interval. If we could get a valid usecase, and the expectations for this 'ly' support, it would be great and I can start working on a PR right away for that.

[simison]

@sampathBlam I don't think it's important and I wouldn't complicate this code for it.

Would you like to pick up this refactor tho? #19

[sampathBlam]

@simison : Does it make sense if i fork/pull from their repo (with their current set of refactorings), resolve the merge conflicts, add more tests if needed, verify and create a new PR?

Or should I first create a PR for their repo on the same branch, thereby, if the PR was accepted in their repo, it would automatically be reflected in #19 ?

[simison]

That sounds good to me 👍

[simison]

There's plenty to do on Agenda side as well so feel free to just dive in. :-)

[sampathBlam]

@simison : Sorry i did not get you. Should I create a new PR or try to update the current one ? The second one might be a slow process.

[simison]

I meant new one as it indeed seems easier. 👍

…

On Sun, 22 Mar 2020, 11:04 Sampath Kumar Krishnan, ***@***.***> wrote: @simison <https://github.com/simison> : Sorry i did not get you. Should I create a new PR or try to update the current one ? The second one might be a slow process. — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub <#8 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AAAVJAD4QAFF5U5XRRK24ETRIXIDHANCNFSM4DRM27VQ> .

[sampathBlam]

@simison : Done. Created a new PR #33