camelcase - So if you guys had a variable with an "ID" in it, would you write it like this: "var userId;" or l - devRant

Ranter

Comments

3

devTea

24382

5y

.
13

ScriptCoded

19290

5y

Man... I can't ever make up my mind about this! But usually userId. Thing is, if I were to write it like userID, how would I write just ID then? All uppercase? That would indicate a class or something else...
16

Coffe2Code

20721

5y

uSeRiD (jAsE case)
2

Skayo

8904

5y

<@norman70688> <@Coffe2Code>
Y'all using jAsE now huh?
12

PaladinRevenant

226

5y

I have fallen into the practice of only capitalizing the first letter of acronyms in camelcase.
userId
parsedJson
I think it preserves the flow of camelcase much better.
3

cafecortado

6809

5y

I'd write "userId" too
4

sudoSandwich

202

5y

++userId
6

Jilano

27304

5y

@Frederick Careful, the jAsE compiler sometimes just deletes itself

I'd go with "userId" even though it hurts.
2

bkwilliams

7431

5y

I should do “UserId” but I end up doing “UserID” because that is what my fingers know how to type.
2

Vuetiful

2312

5y

I use userId. I'm very strict about it. Because this is one of those cases where you search for hours upon hours why userId is undefined.
5

joas

1963

5y

userId

Because userIDGenerator just looks wrong and if it has another acronym after it, it becomes really hard to understand where the first ends and the second starts (eg. userIDDB).
10

ewpratten

9941

5y

user_id
3

AlmondSauce

16719

5y

I'll search for whatever the convention is in the project that I'm working on, and stick with it.
1

AlgoRythm

50984

5y

userid or user_id
1

kescherRant

24533

5y

Project at the company would have it like Id. I hate that convention tho, so I'd say userID.
2

h4xx3r

1717

5y

userId. I prefer to keep the style, always.
1

hack

6518

5y

Golang suggest to use userID, itemID etc
2

1337M0nst3r

148

5y

user.id
OOP MASTER PARADIGM!!!
2

jorgeMachado

34

5y

UserId, because is more clean in my point of view. But UserID (i don't know why) seems more correct.
2

brunofontes

2080

5y

@Frederick No, no, no, jAsE language would change commands names and create and destroy alias from time to time.
1

brunofontes

2080

5y

userId

It's easier to keep the rules than keep remembering exceptions.
2

Wack

6363

5y

Agree with @h4xx3r stick to one style, so `userId` it is.
1

Skayo

8904

5y

Seems like people tend to use "userId".
huh
2

EddieBro

121

5y

user_id.
I have a habit using lowercase & underscore for variables.
3

Gogy

229

5y

If it's the first time in the project then userId, but if someone already wrote userID somewhere I would stick to that for consistency.
1

ShotgunSurgeon

1033

5y

@Skayo Just saw your highlight bot... maybe add a jAsECaSeHiGhLiGhTeR bot. or let the highlighter respond to settings like @higlight :jasecase: some cOdE
0

Skayo

8904

5y

<@ShotgunSurgeon>
Oof sounds like 800 more lines of code haha
1

ShotgunSurgeon

1033

5y

@Skayo But it sure as hell would push the bot 😁
1

kescherRant

24533

5y

@highlight
var userID;
0

highlight

984

5y

@kescherRant
1

Wack

6363

5y

@highlight
var userId
0

highlight

984

5y

@Wack
1

cafecortado

6809

5y

I think I'm going to avoid both and use "idUser" instead
@highlight var idUser;
0

highlight

984

5y

@cafecortado
0

highlight

984

5y

@vlatkozelka
1

kescherRant

24533

5y

@highlight
class User {
val ID;
val firstName;
val secondName;
}
0

highlight

984

5y

@kescherRant
0

kescherRant

24533

5y

secondName should have been lastName. Brainfart!
1

Wack

6363

5y

And id in lowercase...
0

Kyu96

2038

5y

Check out the convention guidelines for the language. In C# its correct to write userId
0

rant1ng

4587

5y

So, words ending in i or l

@highlight

hentaiId

tallId
0

highlight

984

5y

@rant1ng
0

rant1ng

4587

5y

@highlight

Monospace for the win
0

highlight

984

5y

@rant1ng

Related Rants

devRant © 2021 Hexical Labs LLC
Privacy Policy | Terms of Service