Move JS translation file building logic into separate service

Created on 19 August 2019, almost 6 years ago
Updated 30 January 2023, over 2 years ago

Problem/Motivation

Currently, locale.module file consist full logic for building a JS translations file written in old D7 code style. It makes impossible extending this functionality and produces code duplicates.
We should avoid such D7 styling and use OOP style.

Proposed resolution

Use D8 code style and move file building logic from locale.module into separate service. Also, we should mark old methods as @deprecated.

Remaining tasks

None

User interface changes

None

API changes

None

Data model changes

None

Release notes snippet

None

πŸ“Œ Task
Status

Needs work

Version

9.5

Component
LocaleΒ  β†’

Last updated 4 days ago

Created by

πŸ‡ΊπŸ‡¦Ukraine katherine445

Live updates comments and jobs are added and updated live.
Sign in to follow issues

Comments & Activities

Not all content is available!

It's likely this issue predates Contrib.social: some issue and comment data are missing.

  • The Needs Review Queue Bot β†’ tested this issue. It either no longer applies to Drupal core, or fails the Drupal core commit checks. Therefore, this issue status is now "Needs work".

    Apart from a re-roll or rebase, this issue may need more work to address feedback in the issue or MR comments. To progress an issue, incorporate this feedback as part of the process of updating the issue. This helps other contributors to know what is outstanding.

    Consult the Drupal Contributor Guide β†’ to find step-by-step guides for working with issues.

Production build 0.71.5 2024