Skip to content

Generate translations as part of 'test' step and split extensions into 'core' and 'other' #1653

Open
@chrisgarrity

Description

@chrisgarrity

Translation messages are extracted from extension sources by format-message extract using the data passed to the formatMessage

The same message can be used in multiple places, but only the first definition will be extracted. If the same id is used with different default strings the extraction step will raise an error. It would be good to catch those errors before they land in develop.

Currently all extensions are collected into one core translations file. If we want to be able to tell when a language has all the 'required' extensions translated, it would be better to split the extensions into 'core' (i.e. required), and others. The 'others' could be all the rest, or one file per extension.

Metadata

Metadata

Assignees

No one assigned

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions