Option cascading for storeOthersAsComment

Are you requesting a feature, reporting a bug or asking a question?

Bug in code, or bug in documentation.

What is the current behavior?

Some options are configurable at several levels; for example storeOthersAsComment and questionsOrder can be set at the survey level as well as at the question or page level. In case of questionsOrder, the behavior is intuitive: (according to docs, haven’t verified this)

1. The value at the survey level is a default.
2. The value at the page level allows us to change the default for specific pages.

For boolean variables this is different; if you set storeOthersAsComment to false for the survey, then setting it to true for a specific question does not work.

What is the expected behavior?

I would expect boolean variables to cascade, for example when set to null, or simply missing from the JSON, they should take the value from the parent, in this case the survey. Instead the survey level variables seem to do a hard override.

How would you reproduce the current behavior (if this is a bug)?

1. Go here: https://embed.plnkr.co/u88GcOmZm7zrVtwYE1HS/
2. Choose “other”.
3. Type something in the comment field.
4. Click complete.

Provide the test code and the tested page URL (if applicable)

https://embed.plnkr.co/u88GcOmZm7zrVtwYE1HS/

[andrewtelnov]

@SamMousa I have fixed the bug. New unit test is added. The fix will be avalable in the next minor update that we will release tomorrow-aftertomorrow.

Thank you, Andrew

[andrewtelnov]

I made this property invisible. However, I feel we still have to fix the bug.

Thank you, Andrew