It’s so important to use unique names in your code no matter what. It is good practice and makes changes a lot simpler, debugging far easier, and reading through your code a lot kinder on the eyes. Not to mention all the conflicts having the same ID’s can create, which are numerous to say the least.
Very kind to say so Anthony thank you. We are privileged to have such a community and each and every member contributes where and when they can. A true testament of Wappler's founders efforts to include us all in decision making, and make us all feel a part of the product. Rarely experienced this camaraderie outside of very close-knit IRC channels!
I know the naming thing can become tedious but just roll with something like 'create_INPUT_user_name', 'update_INPUT_user_name', 'update_FORM_user' etc. I'm forever updating and forgetting to do this but slowly it is becoming second nature, only took a few years!
We all have different ways of working and try to invent our own methods but it is always good to see what others do.
I have an Excel table with the following, which is very similar to Dave’s suggestion.
Here I’m using DB Table Names and Queries as examples but the logic can be applied to many things including Form Field Inputs etc. Hope this give you food for thought
I think this makes it even more important to stick to a naming convention and keep IDs unique etc.
Having said that, I would distinguish between unique IDs and unique names. I often use the same name more than once on a page. Eg I'll typically have a modal containing an insert form, and another containing an update form, on the same page. I'll use the same names for both forms. I don't think there's a problem with this, and it keeps things simpler.