Fix issues with using
being added erroneously
#31
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.
Fixes #30
It turned out this was only an issue on later scalafix/scalameta versions, so I had to upgrade dependencies to actually reproduce and fix it.
The commit with the actual fix is mrdziuban@c6be468.
The other changes were to address things related to the scalafix upgrade:
templ.body.children
in theSemiAuto
rule instead of justtempl.children
templ.children
returned all the statements within the template, but now it just returns aList
with one element -- the template's body -- so we need to look at the children of the bodyEDIT:
This also fixes an issue where
using
is added to code that's calling a function returned by a method that takesusing
parameters. See example code in #31 (comment)