In order to perform refactoring and to add new features with more confidence, we need unit, integration and end-to-end tests for:

• algorithm parts. Seesrc/algorithms

• React parts - components and pages. See src/components and src/pages

• State management: redux reducers and sagas. See src/state

The infrastructure:

• jest and @testing-libraryare already set up. Un

Feature Description

Have a consistent, documented approach for i18n in sormas-ui.
This should also take into accout sormas-backend and sormas-rest.

Problem Description

It is not always clear which Locale and Language settings apply.
There are at least four sources and well as several cascaded caching mechanisms.
E.g. in #1880 it was noticed that the Locale is not always applied con

@annecori has brought up the fact that the default incidence plots are ambiguous as to when the start and end dates are (e.g. it's difficult to tell if the end of the epicurve contains zero case).

We should include examples in the plotting vignette and the documentation showing that users can supply border = "black" that will show the zero days

The website for epicontacts is sorely out-of-date. For example, the CRAN version has edges_pal() included in the documentation for colors, but it is missing on the website: http://www.repidemicsconsortium.org/epicontacts/reference/colors.html

It becomes a bit awkward to do this because the repo has added features since the last CRAN update, though.

see burnr::sort.fhx()