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
While investigating #41 I discovered we have a bit of a consistency issue with function names. Some functions are "active voice" (verb-noun - e.g. postGlobalStatus, putGameState) while others are "passive voice" (noun-verb - e.g. fieldGoalDisplay, ddDisplay). Some don't even have a verb (e.g. ytgCustom) Since it's rare in English for the object of a verb to come before the verb, I would recommend that we change these to the verb-noun style (e.g. "displayFieldGoalAttempt", "displayDownDistance") or add a verb if needed (e.g. setCustomYtg).
If we tackle this soon we should do it in a branch and test thoroughly because making changes like this could break all kinds of things.
The text was updated successfully, but these errors were encountered:
While investigating #41 I discovered we have a bit of a consistency issue with function names. Some functions are "active voice" (verb-noun - e.g. postGlobalStatus, putGameState) while others are "passive voice" (noun-verb - e.g. fieldGoalDisplay, ddDisplay). Some don't even have a verb (e.g. ytgCustom) Since it's rare in English for the object of a verb to come before the verb, I would recommend that we change these to the verb-noun style (e.g. "displayFieldGoalAttempt", "displayDownDistance") or add a verb if needed (e.g. setCustomYtg).
If we tackle this soon we should do it in a branch and test thoroughly because making changes like this could break all kinds of things.
The text was updated successfully, but these errors were encountered: