Re:Show HN: Ease your dev life with these general naming rules
by khangnd on Sunday January 17, 2021 @01:47AM
(#25808724)
As stated in the repo, you could just go with anything, just pick one for your project, and follow. The general rule that applies here is consistency.
So let's say in PHP, the preferred convention is snake_cake, then use it for the whole project. Then if you are working on a JS project, which the team demands camelCase, then just follow it.
There could be some cases, like in your 3rd example, the team applies camelCase for normal variables, and snake_cake for properties. Again, you still have to follow if it is something the team has agreed.
Re:Show HN: Ease your dev life with these general naming rules
by Akcium on Sunday January 17, 2021 @02:54AM
(#25809031)
Yep, I understand, I just dislike the fact that we'll have 2 types (like fullName and user.first_name + user.last_name), even though it's an agreement.
So let's say in PHP, the preferred convention is snake_cake, then use it for the whole project. Then if you are working on a JS project, which the team demands camelCase, then just follow it.
There could be some cases, like in your 3rd example, the team applies camelCase for normal variables, and snake_cake for properties. Again, you still have to follow if it is something the team has agreed.