We should not jump to disabled fields in the survey
:memo: How is it being implemented?
I have added isEnabled getter to IQuestionView interface
I have implemented isEnabled getter in all custom views
I have modified jumping logic to avoid jump if the next field is disabled
:boom: How can it be tested?
UseCase 1: Login with TZ_TEST_IPC, create a new survey and select Activity = Mjanaja then jumping should work but to found the last disabled field, the jump should be not realized.
:floppy_disk: Requires DB migration?
[x] Nope, we can just merge this branch.
[ ] Yes, but we need to apply it before merging this branch.
[ ] Yes, it's already applied.
:art: UI changes?
[x] Nope, the UI remains as beautiful as it was before!
:pushpin: References
:gear: branches
app: Origin: maintenance/jump_error_if_next_is_disabled Target: v1.4_connect bugshaker-android: Origin: downgrade_gradle_version
EyeSeeTea-SDK: Origin: development
:tophat: What is the goal?
We should not jump to disabled fields in the survey
:memo: How is it being implemented?
:boom: How can it be tested?
UseCase 1: Login with TZ_TEST_IPC, create a new survey and select Activity = Mjanaja then jumping should work but to found the last disabled field, the jump should be not realized.
:floppy_disk: Requires DB migration?
:art: UI changes?