Gather modules' translations from separate files
Description
Environment
Potential Workaround
blocks
is blocked by
relates to
Checklist
hideTestRail: Results
Activity

Mike Taylor February 1, 2018 at 4:20 PM
I guess whatever approach is easiest for you is fine by me. Only I am going to close this issue now because I'm about to include it in stripes-core release 2.9.0 (see https://folio-org.atlassian.net/browse/STCOR-138#icft=STCOR-138), so it might make sense to create a new issue in the STRIPES project for all the modules' changes.

Matt Jones January 31, 2018 at 2:35 PM
I did not create a separate Jira for moving the ui-users translations. I figured most of the UI modules require the same move operation, so I was thinking of linking them back to there. Would you prefer a Jira for each app, or perhaps one for the bulk move, separate form this ticket?

Mike Taylor January 31, 2018 at 7:34 AM
Sounds good! I'll read the PR in a moment.
Let's hold off with the ui-users switch until later today. I will get a stripes-core release done, which it can depend on. This is overdue anyway.
(Is there a separate Jira for the ui-users switch?)

Matt Jones January 31, 2018 at 3:58 AM
Pull requests are up for the stripes-core work and the corresponding translations move in ui-users is pending. Please see description and comments in: https://github.com/folio-org/stripes-core/pull/178
Technically we should have a 2.9.0 release of stripes-core before migrating UI module translations into separate files. While this stripes-core work is backwards compatible with the current package.json approach, the last official 2.8.0 release of stripes-core is not compatible with the new approach.

Mike Taylor December 8, 2017 at 5:46 PM
OK, excellent. Glad to know it's in good hands!
Details
Details
Assignee

Reporter

At present, we gather translations from each module's
package.json
(see STCOR-48). Down the line, we will want to get them from separate files.