error strings should not be capitalized
124 }
125 refDate = refDate.AddDate(0, 0, -(dayOffset))
126 } else {
127 return 0, fmt.Errorf("Unknown day reference: %s", rawRef)128 }
129
130 return refDate.Unix(), nilerror strings should not be capitalized
110 } else if val, err := strconv.Atoi(ref[(len(ref) - 1):]); err == nil {
111 day = val
112 } else {
113 return 0, fmt.Errorf("Day of month required after month name: %s", rawRef)114 }
115 refDate = refDate.AddDate(0, 0, day)
116 } else if len(ref) >= 3 && stringMatchesList(ref[:3], weekdays) { // DayOfWeek (Monday, etc)
Description
Error strings follow a set of guidelines to ensure uniformity and good composability.
Quoting Go Code Review Comments:
Error strings should not be capitalized (unless beginning with
proper nouns or acronyms) or end with punctuation, since they are
usually printed following other context. That is, use
fmt.Errorf("something bad") not fmt.Errorf("Something bad"), so
that log.Printf("Reading %s: %v", filename, err) formats without a
spurious capital letter mid-message.