Open MagicBOTAlex opened 2 weeks ago
IMO in places where the scope is as small as in your example and variables aren't prone to be confused with each other there's not really a benefit in such verbose naming. I agree it's good for bigger scopes but i'd still argue that it's not worth doing a rewrite. Maybe there could be a chapter in the documentation regarding variable naming and best practices. Potentially a glossar for frequently used abbreviations would already go a long way.
ooh, good solution I'd say. And I see your point, just thought I'd suggest it ¯_(ツ)_/¯
Desc
Maybe this is a personal issue, but I found it quite hard to understand, and implement items to the codebase, since many of the variables were quite shortened, with no comments at all. If it's easier for people to participate, then there would likely be more contributors.
It took me multiple hours before understanding this small example code snippet. Now that i understand it, i can easily make changes to it. (I am currently trying to implement another feature.)
In short, it's hard to understand and thus less people would participate.
Example
Original
After
Pros
Cons