I agree. Any time we start annotating type information in the variable name is a missed opportunity to actually use the type system for this.

I suppose this is the "actual" problem with the git setting, in so far as there is an "actual" problem: the variable started out as a boolean, but then quietly turned into a timespan type without triggering warnings on user configs that got reinterpreted as an effect of that.