Naming with well known abbreviations about ios-foundation HOT 7 OPEN

Hey, I was just browsing your discussions (because why not) and thought would chime in. There's a convention for acronym naming in the guidelines: https://twitter.com/arekholko/status/799573361546252288

from ios-foundation.

@fastred welcome to the party mate and thanks for sharing.

For me, this pretty much settles the debate - https://swift.org/documentation/api-design-guidelines/#follow-case-conventions

ping @JohnSundell @onmyway133 @vadymmarkov

from ios-foundation.

I vote option 2, unless the abbreviation is the first word, like urlTask 😄

from ios-foundation.

I vote for option 1, I think it's more consistent. When we have a var url, we can't really name it as URL.

from ios-foundation.

This has been a conundrum for me for some time now, glad to see that someone else also brings it up! My vote is on option 2 with @JohnSundell suggestion. Even if that is more rules to follow, for me it feels like the most natural option.

So it would be something like this:

var url: URL
var urlTask: URLTask
var taskURL: TaskURL

from ios-foundation.

I used to go with taskURL, but I found that taskUrl looks pretty and is more consistent. I treat abbreviation as word, and uppercase the first letter. So I like option 1 more

from ios-foundation.

Seems like we are at a tie here, let the Hunger Games begin, may the odds be ever in your favor.

from ios-foundation.