goNextPageAutomatic not working

[ericdmessick]

Using React version code produced from the dxsurvey service. No bootstrap. This is what I am getting when I run page locally.

I'm doing a range of 1-10. If the user choses any rating less than 5, a new question appears. 5 and over should just complete the page. However, if I click anything over 5+, I get this error:

Uncaught RangeError: Maximum call stack size exceeded

WIth one exception. If I click 10, the question that should only appear for less than 5 appears.

The code I am entering in visibleIf is pretty straight forward.

{question} < 5

Here are the links to the survey. To get to the page in question, answer question in this order:

1. Nope...
2. Yes.
3. I hate you.
4. [THE PAGE IN QUESTION]

https://surveyfordummies.herokuapp.com/

[ericdmessick]

So, I removed the ranking '10'. It only goes up to nine. I don't know why '10' would be cause the conditional to trigger if it was set <5.

However, the error:

Uncaught RangeError: Maximum call stack size exceeded

...still throws if you choose 5-9 and the survey will not complete.

[andrewtelnov]

@ericdmessick You are using the 0.11.1 version. The bug has been fixed in v0.12.0: #238. Please get the latest version: v0.12.1

Thank you,
Andrew

[ericdmessick]

I updated to the new version 0.12.1, but it still does the same thing.

[andrewtelnov]

@ericdmessick Sorry, it is definitely another issue. I have created a plunker example. Could you please fork it, then change it, so it doesn't work and post a new link here.
Because, I do not understand how to reproduce the problem.

Thank you,
Andrew

[ericdmessick]

Okay, I forked it on plunk. It seems to be tied to using the rating to make the next question on that page visible. The second question on that page is set up identically, but completes the page. However, that question does not have a question who's visibility is dependent on it. I just wanted to say, also, that I appreciate this. Whenever I get my hands on a new library, framework, or language, I try to push it to see everything I can do with it. Sometimes, people come off as shitty when something has a bug, or potential bug. I hope that I haven't. I really am greatful. Eric

…

On Wed, Feb 22, 2017 at 1:05 AM, Andrew ***@***.***> wrote: @ericdmessick <https://github.com/ericdmessick> Sorry, it is definitely another issue. I have created a plunker example <http://plnkr.co/edit/CRvWxAF75iRV184qCAg5?p=preview>. Could you please fork, change it, so it doesn't work and post a link here. Because, I do not understand how to reproduce the problem. Thank you, Andrew — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub <#252 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AOkNv3IhS4fyuE8E9m78ic6YKXizbpwYks5re94rgaJpZM4MG4HH> .

[dmitry-kurmanov]

@ericdmessick, Hello! Thank you for the report. I've seen error in the console at your site. I've tried find problem, but you are using min(uglify) version. Could you get version of your site with "dev" bundle that I could debug it, please. Or create fiddle with this error as Andrew said.

PS we are working on functional testing, so we hope that same problems will go away

[ericdmessick]

@dmitrykurmanov I did the plunker fork as requested by @andrewtelnov. Here is a link to the github as well. https://github.com/ericdmessick/SurveyForDummies.git for now.

[andrewtelnov]

@ericdmessick Unfortunately, you did not share a plunker fork link with us. We do not have an access to it :-(
We can take a look on your repo of course.

Thank you,
Andrew

[dmitry-kurmanov]

I've just copy @ericdmessick 's JSON into our editor and here is the bug. So it is not only react version bug.

And I've removed "goNextPageAutomatic" property and it is ok now. So it is "goNextPageAutomatic" bug

[dmitry-kurmanov]

@ericdmessick, we'll fix it. Thanks for your help!

[andrewtelnov]

@ericdmessick There was an call stack overflow if properties goNextPageAutomatic and clearInvisibleValues are set to true.
I have fixed it.

Thank you,
Andrew