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 by splitting it in properties for the const and config for what is not immutable and can assume diff values in each instance.*
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 allocate more memory space.
* The const values will allocate an address in the memory and if we create a class with attributes and its gets to store and return fixed and immutable values it means that we will create many instances and many addresses of memory to store the same constant unnecessary.
Following an illustration
*Class/Object:*
ConfigObject.InstaceA.image = "image value" - memmory address in usage
ConfigObject.InstaceB.image = "image value" - another memmory address in usage
ConfigObject.InstaceC.image = "image value" - another memmory address in usage
*Const*
Means just one memory address with pointers to it.
c/c [~endaphelan] |
|
