Making a clear difference between Option sets, customs states,

Well I don’t know if I’m in the right category, as I thought we could here explain ideas we had, but it seems that this is more a “feature request” category.

Anyway, just to say this, and maybe it could help :

After a month using Bubble, I’m now used to something I couldn’t do without : using personal marks to clearly make the difference between names we gave to Bubble entities :

  • Data Type, only in uppercase : CUSTOMER

  • Fields, first letter uppercase : Name

  • Custom state, adding $, like in the good old Basic times : price$

  • object ID, adding & before : &input_age

This is saving a LOT of time as far as I’m concerned.

Well, I’m curious to know if you have similar manias here :slight_smile:

Michel