You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I'd like to suggest re-evaluating the naming convention for certain configuration parameters. Currently, the parameters use "disable" as a prefix, which increases cognitive load when interpreting their values.
“disable_*=false“ is like a negation of negation (two operation to get the meaning).
Using an “enable_*“ prefix would make it more intuitive and easy to get.
Totally agreed - these are just kinda legacy from before I took over. I'm open to changing them, but won't have time for a while. I brought twins home from the hospital juuuuust a few hours ago 😅
So, if you wanna do it, be my guest. Otherwise... no worries, it'll be a minute though.
I'd like to suggest re-evaluating the naming convention for certain configuration parameters. Currently, the parameters use "disable" as a prefix, which increases cognitive load when interpreting their values.
“disable_*=false“ is like a negation of negation (two operation to get the meaning).
Using an “enable_*“ prefix would make it more intuitive and easy to get.
Parameters:
The text was updated successfully, but these errors were encountered: