Repository navigation
Conditional questions: go to a question based on the value of a linear scale - #3837
AndyScherzinger wants to merge 1 commit into
Conversation
Codecov Report✅ All modified and coverable lines are covered by tests. 📢 Thoughts on this report? Let us know! |
624a98f to
5734f04
Compare
21c5283 to
fe30885
Compare
5734f04 to
6e7c64d
Compare
|
Sorry i didnt have the time to check it currently. But my two cents regarding trigger. For my use case we would need the linear scale as a number input for higher/lower than, which is not possible using choice/options (and is not ideal using number input), for a "How many people do you want to signup" (with Name etc per Person). Thats why i would seperate it from color, as i See no real usecase for color trigger (except some specific quizzes or sth, and then its also possible to use the choice or Text input) |
|
@timedin-de did you already have a look at this feature request? #1728 For me, it sounds a bit more like this is what you would like to achieve? |
fe30885 to
f1898c5
Compare
6e7c64d to
7124f48
Compare
Yes a proper implementation would probably be better, but as you already posted there, its a rather complicated edge case probably not beeing implemented in near future. My case was just this workaround (similar to our current Google forms, [in Gforms we use a nested checkbox "you want to signup more people?]), was: |
|
Ok, but why would you need the linear scale then instead of the radio question? |
I guess Radio doesnt support < and > (so in this use case you would need to have 1 Participant in Branch one, 2 Participants in Branch 2 etc. With < you only need one new Participant per Branch Branch 1: Name 1 vs |
7124f48 to
bdd436e
Compare
b287cc5 to
9214258
Compare
bdd436e to
8e890c3
Compare
8e890c3 to
97c9416
Compare
9214258 to
2e47a17
Compare
97c9416 to
d00994a
Compare
2e47a17 to
b8de1b0
Compare
0bec16a to
24f0959
Compare
91a0a27 to
fc8b80a
Compare
3598ecd to
a1c0441
Compare
711d211 to
51c398d
Compare
a1c0441 to
0bc7c22
Compare
51c398d to
c4ec966
Compare
0bc7c22 to
643e52e
Compare
c4ec966 to
5bbaa47
Compare
643e52e to
d6c463e
Compare
5bbaa47 to
7e93f48
Compare
53b457c to
ca124d6
Compare
156021d to
5f5e67e
Compare
ca124d6 to
1aafc3c
Compare
5f5e67e to
94dfa96
Compare
1aafc3c to
4d8fc92
Compare
94dfa96 to
63723e0
Compare
2e41daa to
1039557
Compare
4a460ff to
d7c866f
Compare
1039557 to
3effcd2
Compare
d7c866f to
db8678b
Compare
3effcd2 to
6883e9e
Compare
Each value of a linear scale gets a row with the same select as on
options, the values at the ends with their labels, e.g. "1 - Strongly
disagree". The jumps are stored in extraSettings.goTo as
{value, target}; as on radio and dropdown questions, there is no
extraSettings.next, and a value without a jump leads to the following
question. A value is an integer from 0 to 10, the range of all scales,
and is matched as a whole number, so "04" counts as 4 as it does for
the answer itself. Narrowing the scale removes the jumps of the values
that are gone, reported in the response header X-Forms-Adjusted.
Based on the linear scale support of #3123 by TimedIn.
Co-Authored-By: TimedIn <git@timedin.net>
Assisted-by: Claude Code:claude-opus-5-5
Signed-off-by: Andy Scherzinger <info@andy-scherzinger.de>
Part 4 of the conditional questions stack, based on #3123 by Micke Nordin with the fixes by TimedIn. Based on #3835; the "Files changed" tab shows only this part.
Stack
This PR
goTowith{value, target}), like Microsoft's Rating.goTo, as radio and dropdown questions; a value without a jump goes to the next question.X-Forms-Adjusted.Tests
IUserFoldererrorsmainalso has on the test instance.🤖 AI (if applicable)