The Name Guy

Naming things is hard, these are some attempts I've made to name things a little less bad.

[Aiera @Aiera]

(1/5) Today's earnings are going to be pretty huge. Following a heated day between congress & big tech CEOs, $AAPL, $AMZN, $GOOGL, & $FB are ALL reporting Q2 earnings today after close. We invite you to #Aieracast these calls in real time tonight so you don’t miss a single thing!

[The Name Guy @theguydotname]

The first thought was to use "access:*", but this can easily be confused with perms based on roles separate from a subscription level, such as an admin vs. normal user. Instead, "unlocked:*" makes it a bit more clear and explicit that these are locked to subscription levels.

[The Name Guy @theguydotname]

We name permissions with a generic "area" or "group" followed by the specific permission, so we can do feature flagging using permission with something like "feature:scheduled_tweets". We recently had to name the set of permissions that belong to a specific subscription level.

[The Name Guy @theguydotname]

"wrapTags" was the winner. Also thought of "groupTags" but since the behavior is specifically about whether or not it can wrap to multiple lines, "wrapTags" sounds more clear and explicit to the person who needs to use it.

[The Name Guy @theguydotname]

So you have a tagged input UI component and need a boolean flag to decide whether the tags should wrap onto multiple lines or truncate at the end of one line with an indicator that there are more. What do you call this flag?