We're updating the issue view to help you get more done. 

Discovery/Make plan to bring translation Library up to date

Description

We use `react-i18next` to manage translation – in `blip` we are currently on version 7.13.0 – the library is currently on 19.8.3 – including breaking changes between v9 and v10. Not only does this represent an issue in just keeping current with libraries we use, it also means that we don't have access to new features specifically the ability to use features that take advantage of hooks (additionally the available documentation now does not match how we use the library which is not helpful when adding/making changes within our code base).

Because the upgrade in between v9 and v10 includes breaking changes this ticket represents figuring out how much that effects our code base and determining what the lift would be to get us current with the library.

Done Criteria

  • Determine a strategy to upgrade react-i18next

Design Specifications:

None

Accessibility Specifications

None

Test Strategy

None

Environment

None

New Fields for Analytics/Export Configuration (if needed)

None

Priority

None

Assignee

Clint Beacock

QA Assignee

None

Reporter

Thacher Hussain

Requested By (External)

None

Fix versions

None

T-Shirt Size

M: <=1 week

Risk Level

None

User Experience Assessment Level

None

UEA: Issue Volume

None

UEA: Category

None

Components

None

Design Review Required?

None

Design Approved By:

None

QA done during validation of another ticket?

None

Accessibility Review Required?

None

Accessibility Review Approved By

None

Approved for Production By:

None

Pull Request Needed

None

Resolved Build #

None

Tech Debt

Medium

Story Points

5

Sprint

Web Sprint 32
Configure