Re:LabelContactRelationYoungerCousinMothersSiblingsDaughterO...
by layer8 on Friday September 22, 2023 @07:21AM
(#37610569)
> The constant embeds everything that an English-speaking localizer needs to explain the relationship in a different language.
I disagree insofar as you really need the explanatory text in the documentation to be able to parse the constant’s name correctly, especially if you’re not already familiar with that specific relationship category. It would also be helpful for the documentation to point to the Chinese/Vietnamese/etc. terms to provide context. In that light, a shorter constant name would have been appropriate IMO, for developer ergonomics.
Even if you want to include “full” information, CNLabelContactRelationYoungerMaleCousinNotViaFathersBrother would have been shorter, if I understand the relationship correctly. (The fact that I’m not entirely sure here also indicates that more documentation is needed.)
I disagree insofar as you really need the explanatory text in the documentation to be able to parse the constant’s name correctly, especially if you’re not already familiar with that specific relationship category. It would also be helpful for the documentation to point to the Chinese/Vietnamese/etc. terms to provide context. In that light, a shorter constant name would have been appropriate IMO, for developer ergonomics.
Even if you want to include “full” information, CNLabelContactRelationYoungerMaleCousinNotViaFathersBrother would have been shorter, if I understand the relationship correctly. (The fact that I’m not entirely sure here also indicates that more documentation is needed.)