Fix issue with loop variable access inside nested foreach statements. #135
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.
Accessing and updating loop variables in a nested foreach does not update the value outside.
Here are 2 scenarios I came across where this was happening:
This seems to be because the foreach loop variables are only stored in the
local
store and not the global context so the nested foreach does not have access to them.I'm not sure the following solution is the correct one, but updating the
src/compile/set.js:getContext
method to merge the local context and the global context seems to fix this issue by making the loop variable available in the global context for the next statements to use.Thank you for this amazing package, it's been super useful to our team!