Deconflict variable names #134
Merged
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
Current coverage is 91.31% (diff: 100%)@@ master #134 diff @@
==========================================
Files 51 52 +1
Lines 1408 1417 +9
Methods 0 0
Messages 0 0
Branches 0 0
==========================================
+ Hits 1285 1294 +9
Misses 123 123
Partials 0 0
|
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.
Svelte was being somewhat cavalier about variable names. With this PR, names that are added to the template scope via
{{#each ...}}blocks are gathered during the validation phase, and then avoided when the code generator is assigning unique variable names. It's not the most sophisticated approach in the world, but it's fast and should be reliable, I think.Fixes #88.