Subsets with API v2
Upgrade Subset
models and services to /v2
to test and improve the new API (genesys-pgr/genesys-server!841) with mapstruct, subset translations and new controllers.
As you upgrade different bits of subset logic in the UI, upgrade all page and related components to use hooks. Don't try to reuse existing base classes, create new solutions that we will be able to use for Datasets (next ticket).
Start with routes in /dashboard
.
i18n in the UI
Since this is a rewrite of Subsets we must also address the issue with multiple i18n keys for the same thing.
We need a model:
namespace (as we have in GGCE) for labels and hints/descriptions of each DTO property (we sometimes use ...public.f..
for these).
The non-model i18n stays where it is, but needs to be reorganized.
Translation support
API now has support to multiple translations of Subset text data (title
and description
). The UI will need to be updated to allow users to manually add and manage translations of the subset (perhaps in a new step?) in the Dashboard.
The user-selected language must be used when displaying a subset (re-enable language selector for Genesys website).
Searching
Ensure that when using full-text search all translated texts are considered. Alternatively we can use only the original language of the dataset + the translation to user's selected language.
In the MR please comment frequently on progress made and include screenshots when appropriate. Work with @ahrybeniuk on API issues.