Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Internalisation: follow data format from the backend #329

Open
Tracked by #320
PascalinDe opened this issue Sep 1, 2023 · 0 comments
Open
Tracked by #320

Internalisation: follow data format from the backend #329

PascalinDe opened this issue Sep 1, 2023 · 0 comments

Comments

@PascalinDe
Copy link
Contributor

The backend e.g. sends the information in the form of

{en: 'english title', de: 'german title', fr: 'french title'}

which gets transformed into flat strings Title, TitleDe and TitleFr, which is less flexible than the data format above. The frontend should follow the Object/Map structure as well to allow for easier handling translations.

@PascalinDe PascalinDe changed the title internalisation: follow data format from the backend Internalisation: follow data format from the backend Sep 1, 2023
@PascalinDe PascalinDe moved this to Todo in D-Voting Sep 27, 2023
@PascalinDe PascalinDe moved this from Todo to Backlog in D-Voting Nov 8, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant