Naming best practices?

[billyfw]

Just curious if there's a document somewhere (that I didn't find) on naming best practices in large apps. In all of the examples, I see pipe-based hierarchies, dots for actions, etc. I'm kind of making my own and trying to avoid "do this 67", but figured it'd be good to avoid obvious mistakes. 

This is the only post I found on it (https://www.googlecloudcommunity.com/gc/AppSheet-Q-A/App-Naming-Conventions/m-p/336636), and not really many replies, so not holding out hope, but figured I'd see. Thanks!

[SkrOYC]

Short answer: there is no naming convention here.

Now, some of us have been using some kind of naming convention that probably evolves every now and then so we can just suggest what we do instead of what is best.

The best advice I have read about naming conventions is be consistent, no matter the way you name things.

[SkrOYC · Accepted solution]

Btw, my suggestions (not necessarily the way I do it for external reasons):

Item	Convention	Comments
Table names	UpperCamelCase	Also use plural
Column names	lowerCamelCase or snake_case	Name your PK with the name of your table on singular + "Id" or "_id". Name your FK with "Id" or "id_" + the name of the table in singular
Views	DatasetName | Usage	This is how I do it actually. Eg.: Employees | MainListView, MainFormView, MainListView, etc
Actions	DatasetName | Efect	Eg.: Tasks | Completed
Slices	SlTableName_purpose Sl_TableName_purpose	Eg.: SlTasks_completed Sl_Tasks_completed

[billyfw]

super, many thanks