-
Notifications
You must be signed in to change notification settings - Fork 89
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
recurrence.next(1) hangs #89
Comments
I guess it is not possible to have compound intervals.
|
Just hit this bug also! Such a pain in the neck. Rolling back to version 1.0.5 it works fine |
You are starting your recurrence on a Monday and asking for every 3 weeks, which will always be a Monday, but then also saying to only match Tuesdays, so it will never match anything. |
Wouldn’t the expected behaviour be to throw an error? Currently it freezes the entite process or crashes the browser. In version 1.0.5 it works perfectly. |
I think expected result would be to return an empty array (nothing matches this query). |
That makes sense. What is different between 1.0.5 and current version?
… On 9 Apr 2018, at 6:18 am, Jeff Barnes ***@***.***> wrote:
I think expected result would be to return an empty array (nothing matches this query).
The reason it never returns is the code is busy looking for a date that will match these conditions that doesn't exist and will try all dates until the end date.
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub, or mute the thread.
|
Any response to this? It works perfectly in 1.0.5 but crashes javascript 1.0.7 |
I find that the recur.maches function works perfectly ,so I use my own next function to solve this issue temporary, maybe it's helpful for someone, you can change the function to return an array if you need
|
@Hyperblaster thanks! I've rollback to version 1.0.5 and works perfectly. |
Hi,
This script hangs the browser. Is there a bug?
Jake He #
The text was updated successfully, but these errors were encountered: