Closed JabberWocky-22 closed 1 month ago
i'm willing to accept this, but i have to review it carefully.
Please make sure to add extensive tests, cron is devil in case of matrix cases ;-)
I have rebased to master, fixed the test and added more. Please take some time to review :) @kiorky
Besides:
I also fixed a bug which https://github.com/kiorky/croniter/pull/42 doesn't cover(range)
Ensure match_range
return False
when not previous value avaliable
Sorry for mix them up.
I have rebased to master, fixed the test and added more. Please take some time to review :) @kiorky
Besides: I also fixed a bug which #42 doesn't cover(range) Ensure
match_range
returnFalse
when not previous value avaliable Sorry for mix them up.
yes i saw, this worries me, can you make a separate PR for this, i ll merge it way faster that this one that should be scopped as it is already invasive.
but how did you rebase, as there are 3 commits, can you just make a PR with the match_range problem, then rebase (as git rebase -i
) on top of it ?
I have made 2 separate bug fix PR.
I just rebase this PR to master and didn't squash the commits. Some projects dislike squash and force-push. I will squash it after it's ok.
Damn, i m so sorry, seems the review i already did yesterday wasnt published. So some (yesterday) comments may be out of date.
What i propose to you is to make the other PR #82 merged, then you rebase this PR, then i ll ensure the review is up to date ...
So please now rebase this one to see the final diff that should have a lift :)
(you should obtain something similar to https://github.com/kiorky/croniter/compare/master...y )
There is a bug with the comment posts, give me a minute to sort it out ...
There is a bug with the comment posts, give me a minute to sort it out ...
you can proceed, sorry for the noise :)
So, so far so good, merging, and a lot of thanks for applying those review modifications, along to the 2 other PRs !
released as 3.0.0 https://pypi.org/project/croniter/3.0.0/
support year at the seventh field.