IMHO:
- We need to move forward with the config.go file and suggestion by adding first the const ( which will be done by [~lfitzgerald] in her PR)
- Then we need analysed the MSS-Operator code/project and check which should be in the config.go.
- *So, just if we find code impl which is NOT only a const makes sense move forward with [~endaphelan] suggestion of it be a struct/object.*
h4. IMPORTANT:
* Usually, when a project is designed it is called properties files which are made by the constant. No make sense to have an object to return just/only const values, it will not follow the good practices and will use allocated allocate more space of the memory space .
* The cost const values will allocate an address in the memory and if we create a class to store fixed values and immutable values it means that we will create many instances of the same fixed and immutable values in many addresses of memory to store the same constant unnecessary.
ConfigObject.InstaceA.image = "image value"
ConfigObject.InstaceB.image = "image value"
ConfigObject.InstaceC.image = "image value"
c/c [~endaphelan] |
|
