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

[web] Always send a language header in all requests #8612

Closed
1 task
exalate-issue-sync bot opened this issue Mar 15, 2023 · 0 comments · Fixed by #8621
Closed
1 task

[web] Always send a language header in all requests #8612

exalate-issue-sync bot opened this issue Mar 15, 2023 · 0 comments · Fixed by #8621
Assignees
Labels

Comments

@exalate-issue-sync
Copy link

Description

Most of the translations happen in web itself. Notifications are about to be translated backend side, i.e. web will receive already translated content. We might provide translated error messages in the future. So it makes sense to always let the backend know about the language of the user.

User Stories

  • As user i want to have a UI translated in my preferred language to understand it better

Value

Acceptance Criteria

Definition of ready

[ ] everybody needs to understand the value written in the user story
[ ] acceptance criteria has to be defined
[ ] all dependencies of the user story need to be identified
[ ] feature should be seen from an end user perspective
[ ] user story has to be estimated
[ ] story points need to be less then 20

Definition of done

  • Functional requirements
    [ ] functionality described in the user story works
    [ ] acceptance criteria are fulfilled
  • Quality
    [ ] code review happened
    [ ] CI is green
    [ ] critical code received unit tests by the developer
    [ ] automated tests passed (if automated tests are not available, this test needs to be created and passed
  • Non-functional requirements
    [ ] no sonar cloud issues
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant