Add further detail to uses of Pause If and Measured If with Measured#255
Merged
Conversation
Differentiating between whether to use Pause If or Measured If comes up a fair bit in jr-dev chat. A lot of times it is assumed you'd only use Measured If. Since there is a behavioral difference between the two where they each have unique use cases, this PR adds some additional detail and organization to the scope-limiting section to make it more visible and hopefully guide developers more effectively in choosing which to use.
wescopeland
approved these changes
Jun 27, 2025
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
Differentiating between whether to use Pause If or Measured If comes up a fair bit in jr-dev chat. A lot of times it is assumed you'd only use Measured If. Since there is a behavioral difference between the two where they each have unique use cases, this PR adds some additional detail and organization to the scope-limiting section to make it more visible and hopefully guide developers more effectively in choosing which to use.