Add 'both' in random order to RangeOfMotion tasks #1403
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Update to latest version
Update to RK master
Change 'extend' for 'raise', since the former was not anatomically correct. Also, add required instructions when both limbs are being measured in the same task.
If .excludeInstructions option was selected, the previous brace positions would exclude the touchAnywhere and RoM steps
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This pull requests deals with issue #1401
The knee and shoulder Range of Motion tasks will behave as previously when 'right' or 'left' is passed as an argument, but 'both' is also now a valid argument.
When 'both' is passed, left and right RoM tasks will be presented in random order. Some additional instructions have been added to inform the user that two measurements will be taken in sequence, and to link the two tasks.
The changes are largely based on the existing Tapping task.