search

ice-cube-ruby / ice_cube

Ruby Date Recurrence Library - Allows easy creation of recurrence rules and fast querying
MIT License
2.41k stars 358 forks source link

start_time constructor argument isn't working properly? #539

Closed buxbunny110 closed 1 year ago

buxbunny110 commented 1 year ago

I got really strange case, I'm getting nuts let me explain why here are two scenarios image This is normal case where when I put 'Time.now' and put times within certain timeframe it's working as expected, however... image as you can see when I built times with specified times, it's not working anymore, one subtle thing I noticed is that, when I create time with Time.now, it gives me output with microseconds whereas with constructor it omit them, anyone knows what it could be?

buxbunny110 commented 1 year ago

Btw, if I specify only end_time and omit the start_time, it seems to be working, looks like start_time has sort of issue.

buxbunny110 commented 1 year ago

I got something, this is working image

buxbunny110 commented 1 year ago

I had to use occurring_at? rather than occurs_at? my bad, issue can be closed, btw it would be great if there be more explanations that would help to differentiate between them.