Code Review & Rename Fields According to Naming Convention Standard

[ChernenkoVitaliy]

Description

Summary:

We need to review the current codebase and ensure that the field names are following the established naming conventions for multi-language translation fields in Java classes. Specifically, we want to adhere to the following naming conventions:

• Fields representing Ukrainian data should be suffixed with Uk (e.g., titleUk, descriptionUk).
• Fields representing English data should be suffixed with En (e.g., titleEn, descriptionEn).
• We should avoid using non-standard language codes (e.g., titleUa).
• All field names should be in camelCase format.
• All changes should be synced with the UI team to avoid breaking the code and ensure seamless integration between the frontend and backend.

Tasks:

• Review the existing Java classes that contain translation fields (e.g., HabitTranslationDto) and ensure the fields are named according to the above conventions.
• Rename any incorrectly named fields:
  • For Ukrainian fields, rename suffixes like Ua to Uk.
• Ensure that the fields are consistent with standatds (Uk for Ukrainian, En for English).

Example of Correct Naming:

public class HabitTranslationDto {
    private String description;
    private String habitItem;
    private String languageCode;
    private String name;
    private String descriptionUk;  // Ukrainian description
    private String nameUk;         // Ukrainian name
    private String habitItemUk;    // Ukrainian habit item
}