Generated Java-classes naming convention

[OleksandrShkurat]

Hello guys. I've just started using this library and the first question I have is about the generated Java-classes naming convention. I see the following non-habitant cases:

• DglConstants contains inner classes and they are named as typical Java constants (SCREAMING_SNAKE_CASE) instead of being named as just regular classes (UpperCamelCase): QUERY instead of Query and other custom class definitions with the same style.
• Those inner classes have constants that are named as typical Java classes (UpperCamelCase) instead of being named as constants (SCREAMING_SNAKE_CASE)

I tried to find some explanation why in this exact library those generated code members should be named exactly like this, but without any luck. Is it a kind of intentional separating the code style from the wide-spreading typical Java code naming convention to make the code visually different or just a naming habit given from another platform?

[paulbakker]

The reason for both is really just to make it read as nicely as possible, instead of strictly following conventions. If it's actually nicer to read is mostly preference I guess, so it's not a very strong argument.

Since this is more a question, and it's very unlikely that we'll ever change it, I'll close this issue.