On Thursday, May 16, 2024 at 9:21:47 PM UTC-6 Bob wrote:
What's i18n message key string case style is recommend? I've reviewed the current i18n message key string case style conventions. In the core, it is already in a very chaotic state. Not to mention in various plugins. some file use PascalCase like: core/src/main/resources/hudson/cli/Messages.properties some file use camelCase like: core/src/main/resources/jenkins/console/Messages.properties some file use snake_case like: core/src/main/resources/hudson/model/Cause/UserIdCause/description.properties some file even mix under_score and CamelCase naming conventions. like: core/src/main/resources/jenkins/install/Messages.properties If there were no previous conventions regarding this matter, can we reach a new consensus on which naming style to use in new files? To be honest, every time I need to add a new message key, I hesitate for quite some time. I believe there were no conventions previously because the initial default is to use a form of the original message text as the name of the property. I prefer the camel case format because the properties are fields of their associated Messages class in Java. I prefer to not change the existing property names due to the risk of mistakes and surprises from that type of renaming exercise. I'm open to other ways of thinking Mark Waite -- You received this message because you are subscribed to the Google Groups "Jenkins Developers" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-dev+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/8517e0fd-79cb-4ff1-aaab-417cf4ad1990n%40googlegroups.com.
