Skip to:

  1. Skip to Jira Navigation
  2. Skip to Side Navigation
  3. Skip to Main Content

SPIKE: Centralizing country and language data in stripes components

Description

Overview:
Would like to write a few stories about centralizing country and language data in stripes-components but want to check in with Thunderjet first. Maybe there are legit reasons for stripes-acq-components to maintain its own lists for these data?

Background:
It seems like the list of languages in various places in FOLIO UI is data - or Localize - driven these days instead of using the old languages.json file.

We have a client that need to add language codes to this list from the iso639-3 standard (one example: https://iso639-3.sil.org/code/yue) and I am sure there are other lists around the corner as well

Scenarios:
TBD

  1. Scenario:

    • Given <preconditions>

    • When <actions>

    • Then <results>

  2. Scenario:

    • Given <preconditions>

    • When <actions>

    • Then <results>

Environment

None

Potential Workaround

None

CSP Approved

None

CSP Request Details

None

Checklist

hide

TestRail: Results

Activity

Show:

Zak Burke February 19, 2021 at 7:22 PM

LGTM. Nice work, !

Aliaksei Chumakou February 19, 2021 at 6:39 PM

Could you please check if anything more required? Thanks

Aliaksei Chumakou February 19, 2021 at 2:24 PM

 it looks like no business value to support separate list of languages and countries for Acquisitions, so I switched to stripes-components lists. 

Done

Details

Assignee

Reporter

Tester Assignee

Labels

Priority

Story Points

Sprint

Development Team

Thunderjet

Fix versions

TestRail: Cases

Open TestRail: Cases

TestRail: Runs

Open TestRail: Runs

Created February 11, 2021 at 4:14 PM
Updated May 5, 2021 at 8:25 PM
Resolved February 22, 2021 at 8:48 AM
TestRail: Cases
TestRail: Runs