Currently, when utilising the Localize-It Action, it is required to manually adjust the key naming to align with a specific standard (e.g., PascalCase or snake_case). This manual adjustment introduces unnecessary friction and potential for inconsistencies in the naming convention across different users and projects.
Enhancement Proposal:
To streamline the user experience and ensure consistency in key naming, I propose implementing an automated key naming convention suggestion feature within the string extraction process.
Proposed Functionality:
Key Naming Convention Identification: Based on user preferences or project settings, the system should identify the preferred key naming convention (e.g., PascalCase, snake_case).
Automated Key Generation: Utilising the identified naming convention, the system should create an appropriate key for the extracted string.
Benefits:
Improved Efficiency: Eliminates the need for manual key naming adjustments, saving users time and effort.
Consistency: Ensures consistency in key naming conventions across projects and users, enhancing code readability and maintainability.
User Flexibility: Users can still manually adjust suggested keys if needed, providing flexibility while promoting standardisation.
Enhanced User Experience: Streamlines the string extraction process, enhancing overall user satisfaction with the feature.
Description:
Issue Overview:
Currently, when utilising the Localize-It Action, it is required to manually adjust the key naming to align with a specific standard (e.g., PascalCase or snake_case). This manual adjustment introduces unnecessary friction and potential for inconsistencies in the naming convention across different users and projects.
Enhancement Proposal:
To streamline the user experience and ensure consistency in key naming, I propose implementing an automated key naming convention suggestion feature within the string extraction process.
Proposed Functionality:
Benefits: