Closed dseevr closed 8 years ago
oh, this is because ineffassign got bug fixes in IT that caused it to detect new ones. I ran into this the other night preparing the DB patch.
Ahh, that explains... and because we have to invoke ineffassign once for each dir, it was just bailing on the first error.
Do you want me to tidy up all the spots it's complaining about and update the PR?
If you don't mind; yeah.
Done and passing
hmm; I made several of these fixes already in the db patch but I guess I can rebase them out
LGTM. Simple enough that I'm just going to merge it.
This fixes all the issues which the new version of ineffassign is complaining about.