-
Notifications
You must be signed in to change notification settings - Fork 397
Improve localization model validation #3254
Copy link
Copy link
Open
Labels
Priority:3Work that is nice to haveWork that is nice to havearea: authoringEnhancements to the process of authoring, maintaining, and testing templatesEnhancements to the process of authoring, maintaining, and testing templatesgood first issueeasy issue, good for first-time contribution to the repoeasy issue, good for first-time contribution to the repotriagedThe issue was evaluated by the triage team, placed on correct area, next action defined.The issue was evaluated by the triage team, placed on correct area, next action defined.
Milestone
Description
Metadata
Metadata
Assignees
Labels
Priority:3Work that is nice to haveWork that is nice to havearea: authoringEnhancements to the process of authoring, maintaining, and testing templatesEnhancements to the process of authoring, maintaining, and testing templatesgood first issueeasy issue, good for first-time contribution to the repoeasy issue, good for first-time contribution to the repotriagedThe issue was evaluated by the triage team, placed on correct area, next action defined.The issue was evaluated by the triage team, placed on correct area, next action defined.
Type
Fields
Give feedbackNo fields configured for issues without a type.
Localization model should be further validated by checking:
and showing warnings/errors if they are missing.
localization should be validated for all locales and then during standard installation, only current (or best match) locale should be returned by RunnableProjectGenerator.GetTemplatesAndLangpacksFromDir