Add loop metadata. #66
Merged
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.
Proposed Changes
This PR adds functionality that exposes some information about the loop currently being executed.
A
loopobject is constructed and passed into thelocalsof the loop being executed.Inside a loop, you now have access to the following variables:
loop.index- the current iteration of the loop (0 indexed)loop.remaining- number of iterations until the end (0 indexed)loop.first- boolean indicating if it's the first iterationloop.last- boolean indicating if it's the last iterationloop.length- total number of itemsUsage
Nested loops
The
loopobject contains information about the current loop.This means you can't access the
loop.remainingvariable of the parent loop.A possible solution, though outside the scope of this PR, would be for the
<each>tag to accept alocals=""attribute, which could be used to pass down data - in this case, the parent loop's metadata.Types of Changes
Checklist
If merged, this PR closes #65