Make luacheck >= 0.26 happy#9174
Conversation
|
I'm afraid I don't like this PR much. I definitely appreciate the effort though. :-) With regard to the _ stuff, I haven't found the time to submit a patch to upstream luacheck to make the specifics configurable, but I don't think changing what's And I'm not at all fond of the logic changes either. The dumb algorithm that should keep its stupid mouth shut about which way we decide the logic is most expressive and comprehensible about its intent. Related: |
|
I take back what I said about the logic changes. I think those look like improvements in clarity, meaning I think luacheck makes sense there and no global override is necessary in my eyes, only (theoretically) local ones. Edit: I was mainly responding to the "make luacheck happy" commit message rather than to the actual changes on that one, mea culpa. |
|
Well, when reading first @Frenzie 's comment, I was fearing there would be lots of changes in many of (my) places :) |
|
I'd rather use |
That would have been my choice if I hadn't already peppered a few |
Frenzie
left a comment
There was a problem hiding this comment.
That would have been my choice if I hadn't already peppered a few this across the codebase ;p.
Seeing this feels a bit foreign (perhaps more like JS, although in JS I used to do a lot of self = this to keep a reference because this can be quite variable), but if you say the code is already "peppered" with it. ;-)
Re: koreader/koreader-base#1487
This change is